OID reference

vrrpOperationsRowStatus

1.3.6.1.2.1.68.1.7.1.14

Description

The RowStatus variable should be used in accordance to installation and removal conventions for conceptual rows. When `vrrpOperationsRowStatus' is set to active(1), no other objects in the conceptual row can be modified. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWai…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.2.1.68.1.7.1 (vrrpOperationsEntry)
Node code
14
Node name
vrrpOperationsRowStatus
Category
SNMP management object
Numeric OID
1.3.6.1.2.1.68.1.7.1.14
URN notation
urn:oid:1.3.6.1.2.1.68.1.7.1.14
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 2 1 68 1 7 1 14}

  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrpMIB(68) vrrpOperations(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrpMIB(68) vrrpMIB(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrpMIB(68) vrrpv3Objects(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrp(68) vrrpOperations(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrp(68) vrrpMIB(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrp(68) vrrpv3Objects(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrpv3MIB(68) vrrpOperations(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrpv3MIB(68) vrrpMIB(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) vrrpv3MIB(68) vrrpv3Objects(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) vrrpMIB(68) vrrpOperations(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) vrrpMIB(68) vrrpMIB(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) vrrpMIB(68) vrrpv3Objects(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) vrrp(68) vrrpOperations(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) vrrp(68) vrrpMIB(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) vrrp(68) vrrpv3Objects(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) vrrpv3MIB(68) vrrpOperations(1) vrrpOperationsTable(7) vrrpOperationsEntry(1) vrrpOperationsRowStatus(14)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/2/1/68/1/7/1/14
  • /ISO/Identified-Organization/6/1/2/1/68/1/7/1/14
  • /ISO/3/6/1/2/1/68/1/7/1/14
Named path variants
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrpMIB/vrrpOperations/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrpMIB/vrrpMIB/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrpMIB/vrrpv3Objects/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrp/vrrpOperations/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrp/vrrpMIB/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrp/vrrpv3Objects/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrpv3MIB/vrrpOperations/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrpv3MIB/vrrpMIB/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/vrrpv3MIB/vrrpv3Objects/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib/vrrpMIB/vrrpOperations/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib/vrrpMIB/vrrpMIB/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib/vrrpMIB/vrrpv3Objects/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib/vrrp/vrrpOperations/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib/vrrp/vrrpMIB/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib/vrrp/vrrpv3Objects/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • /iso/identified-organization/dod/internet/mgmt/mib/vrrpv3MIB/vrrpOperations/vrrpOperationsTable/vrrpOperationsEntry/vrrpOperationsRowStatus
  • Additional combinations skipped.

SNMP properties

Value type
RowStatus
Maximum access defined by MIB
read-create
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.

Product context

Documented MIB packages

The FS.COM catalogue lists MIB packages containing this definition for these models:

N5860-48SC, N8560-32C, N8560-48BC, N8560-64C, NC8200-16Q, NC8200-24BC, NC8200-4TD, NC8200-8C, NC8400-16CD, NC8400-32C, NC8400-4TH, S3100-16TF.

Show 11 more models

S3410-24TS-P, S3910-24TS, S3910-48TS, S5810-28FS, S5810-28TS, S5810-48FS, S5810-48TS, S5810-48TS-P, S5860-20SQ, S5860-24XB-U, S5860-48SC.

A definition in a model's MIB package does not establish that the device implements it or permits access.

Available source records contain 5 distinct definitions; some records may not include a definition.

Show 5 published definitions

vrrpOperationsRowStatus · current

vrrpOperationsRowStatus OBJECT-TYPE  
           SYNTAX       RowStatus  
           MAX-ACCESS   read-create  
           STATUS       current  
           DESCRIPTION  
               "The RowStatus variable should be used in accordance to 
               installation and removal conventions for conceptual  
               rows. When `vrrpOperationsRowStatus' is set to  
               active(1), no other objects in the conceptual row can 
               be modified. 
        
               To create a row in this table, a manager sets this  
               object to either createAndGo(4) or createAndWait(5).  
               Until instances of all corresponding columns are  
               appropriately configured, the value of the  
               Corresponding instance of the `vrrpOperationsRowStatus' 
               column will be read as notReady(3).   
               In particular, a newly created row cannot be made  
               active(1) until (minimally) the corresponding instance  
               of vrrpOperationsInetAddrType, vrrpOperationsVrId and  
               vrrpOperationsPrimaryIpAddr has been set and there is  
               at least one active row in the  
               `vrrpAssociatedIpAddrTable' defining an associated  
               IP address. 
    
               notInService(2) should be used to administratively  
               bring the row down. 
    
               A typical order of operation to add a row is: 
               1. Create a row in vrrpOperationsTable with  
               createAndWait(5). 
               2. Create one or more corresponding rows in 
               vrrpAssociatedIpAddrTable. 
               3. Populate the vrrpOperationsEntry. 
               4. set vrrpOperationsRowStatus to active(1). 
    
               A typical order of operation to delete an entry is: 
               1. Set vrrpOperationsRowStatus to notInService(2). 
               2. Set the corresponding rows in  
               vrrpAssociatedIpAddrTable to destroy(6) to delete the  
               entry.  
               3. set vrrpOperationsRowStatus to destroy(6) to delete  
               the entry."   
           ::= { vrrpOperationsEntry 14 }

vrrpOperationsRowStatus · current

vrrpOperationsRowStatus          OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The RowStatus variable should be used in accordance to installation
         and removal conventions for conceptual rows. When
         `vrrpOperationsRowStatus' is set to active(1), no other objects in the
         conceptual row can be modified.

         To create a row in this table, a manager sets this object to either
         createAndGo(4) or createAndWait(5). Until instances of all
         corresponding columns are appropriately configured, the value of the
         corresponding instance of the `vrrpOperationsRowStatus' column will be
         read as notReady(3). In particular, a newly created row cannot be made
         active(1) until (minimally) the corresponding instance of
         vrrpOperationsInetAddrType, vrrpOperationsVrId and
         vrrpOperationsPrimaryIpAddr has been set and there is at least one
         active row in the `vrrpAssociatedIpAddrTable' defining an associated
         IP address.

         notInService(2) should be used to administratively bring the row down.

         A typical order of operation to add a row is: 1. Create a row in
         vrrpOperationsTable with createAndWait(5). 2. Create one or more
         corresponding rows in vrrpAssociatedIpAddrTable. 3. Populate the
         vrrpOperationsEntry. 4. set vrrpOperationsRowStatus to active(1).

         A typical order of operation to delete an entry is: 1. Set
         vrrpOperationsRowStatus to notInService(2). 2. Set the corresponding
         rows in vrrpAssociatedIpAddrTable to destroy(6) to delete the entry.
         3. set vrrpOperationsRowStatus to destroy(6) to delete the entry."
    ::= { vrrpOperationsEntry 14 }

vrrpOperationsRowStatus · current

vrrpOperationsRowStatus OBJECT-TYPE  
        SYNTAX       RowStatus  
        MAX-ACCESS   read-create  
        STATUS       current  
        DESCRIPTION  
            "The RowStatus variable should be used in accordance to 
            installation and removal conventions for conceptual  
            rows. When `vrrpOperationsRowStatus' is set to  
            active(1), no other objects in the conceptual row can 
            be modified. 
     
            To create a row in this table, a manager sets this  
            object to either createAndGo(4) or createAndWait(5).  
            Until instances of all corresponding columns are  
            appropriately configured, the value of the  
            corresponding instance of the `vrrpOperationsRowStatus' 
            column will be read as notReady(3).   
            In particular, a newly created row cannot be made  
            active(1) until (minimally) the corresponding instance  
            of vrrpOperationsInetAddrType, vrrpOperationsVrId and  
            vrrpOperationsPrimaryIpAddr has been set and there is  
            at least one active row in the  
            `vrrpAssociatedIpAddrTable' defining an associated  
            IP address. 
 
            notInService(2) should be used to administratively  
            bring the row down. 
 
            A typical order of operation to add a row is: 
            1. Create a row in vrrpOperationsTable with  
            createAndWait(5). 
            2. Create one or more corresponding rows in 
            vrrpAssociatedIpAddrTable. 
            3. Populate the vrrpOperationsEntry. 
            4. set vrrpOperationsRowStatus to active(1). 
 
            A typical order of operation to delete an entry is: 
            1. Set vrrpOperationsRowStatus to notInService(2). 
            2. Set the corresponding rows in  
            vrrpAssociatedIpAddrTable to destroy(6) to delete the  
            entry.  
            3. set vrrpOperationsRowStatus to destroy(6) to delete  
            the entry."  
        ::= { vrrpOperationsEntry 14 }

vrrpOperationsRowStatus · current

vrrpOperationsRowStatus OBJECT-TYPE
        SYNTAX       RowStatus
        MAX-ACCESS   read-create
        STATUS       current
        DESCRIPTION
            "The RowStatus variable should be used in accordance to
            installation and removal conventions for conceptual
            rows. When `vrrpOperationsRowStatus' is set to
            active(1), no other objects in the conceptual row can
            be modified.

            To create a row in this table, a manager sets this
            object to either createAndGo(4) or createAndWait(5).
            Until instances of all corresponding columns are
            appropriately configured, the value of the
            corresponding instance of the `vrrpOperationsRowStatus'
            column will be read as notReady(3).
            In particular, a newly created row cannot be made
            active(1) until (minimally) the corresponding instance
            of vrrpOperationsInetAddrType, vrrpOperationsVrId and
            vrrpOperationsPrimaryIpAddr has been set and there is
            at least one active row in the
            `vrrpAssociatedIpAddrTable' defining an associated
            IP address.

            notInService(2) should be used to administratively
            bring the row down.

            A typical order of operation to add a row is:
            1. Create a row in vrrpOperationsTable with
            createAndWait(5).
            2. Create one or more corresponding rows in
            vrrpAssociatedIpAddrTable.
            3. Populate the vrrpOperationsEntry.
            4. set vrrpOperationsRowStatus to active(1).

            A typical order of operation to delete an entry is:
            1. Set vrrpOperationsRowStatus to notInService(2).
            2. Set the corresponding rows in
            vrrpAssociatedIpAddrTable to destroy(6) to delete the
            entry.
            3. set vrrpOperationsRowStatus to destroy(6) to delete
            the entry."
        ::= { vrrpOperationsEntry 14 }

vrrpOperationsRowStatus · current

vrrpOperationsRowStatus OBJECT-TYPE  
    SYNTAX       RowStatus  
    MAX-ACCESS   read-create  
    STATUS       current  
    DESCRIPTION  
        "The RowStatus variable should be used in accordance to 
        installation and removal conventions for conceptual  
        rows. When `vrrpOperationsRowStatus' is set to  
        active(1), no other objects in the conceptual row can 
        be modified. 
 
        To create a row in this table, a manager sets this  
        object to either createAndGo(4) or createAndWait(5).  
        Until instances of all corresponding columns are  
        appropriately configured, the value of the  
        corresponding instance of the `vrrpOperationsRowStatus' 
        column will be read as notReady(3).   
        In particular, a newly created row cannot be made  
        active(1) until (minimally) the corresponding instance  
        of vrrpOperationsInetAddrType, vrrpOperationsVrId and  
        vrrpOperationsPrimaryIpAddr has been set and there is  
        at least one active row in the  
        `vrrpAssociatedIpAddrTable' defining an associated  
        IP address. 
 
        notInService(2) should be used to administratively  
        bring the row down. 
 
        A typical order of operation to add a row is: 
        1. Create a row in vrrpOperationsTable with  
        createAndWait(5). 
        2. Create one or more corresponding rows in 
        vrrpAssociatedIpAddrTable. 
        3. Populate the vrrpOperationsEntry. 
        4. set vrrpOperationsRowStatus to active(1). 
 
        A typical order of operation to delete an entry is: 
        1. Set vrrpOperationsRowStatus to notInService(2). 
        2. Set the corresponding rows in  
        vrrpAssociatedIpAddrTable to destroy(6) to delete the  
        entry.  
        3. set vrrpOperationsRowStatus to destroy(6) to delete  
        the entry."  
    ::= { vrrpOperationsEntry 14 }

Meaning

Descriptions

2 unique

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

Description 1

The RowStatus variable should be used in accordance to installation and removal conventions for conceptual rows. When `vrrpOperationsRowStatus' is set to active(1), no other objects in the conceptual row can be modified. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the Corresponding instance of the `vrrpOperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpOperationsInetAddrType, vrrpOperationsVrId and vrrpOperationsPrimaryIpAddr has been set and there is at least one active row in the `vrrpAssociatedIpAddrTable' defining an associated IP address. notInService(2) should be used to administratively bring the row down. A typical order of operation to add a row is: 1. Create a row in vrrpOperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpAssociatedIpAddrTable. 3. Populate the vrrpOperationsEntry. 4. set vrrpOperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpOperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpAssociatedIpAddrTable to destroy(6) to delete the entry. 3. set vrrpOperationsRowStatus to destroy(6) to delete the entry.

Sources for this description

FS.COM official Documentation Hub native MIB packages

See 1 matching source record

Description 2

The RowStatus variable should be used in accordance to installation and removal conventions for conceptual rows. When `vrrpOperationsRowStatus' is set to active(1), no other objects in the conceptual row can be modified. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the `vrrpOperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpOperationsInetAddrType, vrrpOperationsVrId and vrrpOperationsPrimaryIpAddr has been set and there is at least one active row in the `vrrpAssociatedIpAddrTable' defining an associated IP address. notInService(2) should be used to administratively bring the row down. A typical order of operation to add a row is: 1. Create a row in vrrpOperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpAssociatedIpAddrTable. 3. Populate the vrrpOperationsEntry. 4. set vrrpOperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpOperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpAssociatedIpAddrTable to destroy(6) to delete the entry. 3. set vrrpOperationsRowStatus to destroy(6) to delete the entry.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Common and standard MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copiesNokia networking MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

2 records

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

Records for description 1FS.COM official Documentation Hub native MIB packages1 record · 1 source

Description 1

vrrpOperationsRowStatus · currentFS.COM official Documentation Hub native MIB packages1 source

Status in source: current.

Names: vrrpOperationsRowStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "vrrpOperationsRowStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "RowStatus",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The RowStatus variable should be used in accordance to installation and removal conventions for conceptual rows. When `vrrpOperationsRowStatus' is set to active(1), no other objects in the conceptual row can be modified. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the Corresponding instance of the `vrrpOperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpOperationsInetAddrType, vrrpOperationsVrId and vrrpOperationsPrimaryIpAddr has been set and there is at least one active row in the `vrrpAssociatedIpAddrTable' defining an associated IP address. notInService(2) should be used to administratively bring the row down. A typical order of operation to add a row is: 1. Create a row in vrrpOperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpAssociatedIpAddrTable. 3. Populate the vrrpOperationsEntry. 4. set vrrpOperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpOperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpAssociatedIpAddrTable to destroy(6) to delete the entry. 3. set vrrpOperationsRowStatus to destroy(6) to delete the entry.\"",
    "::=",
    "{",
    "vrrpOperationsEntry",
    "14",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RowStatus"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The RowStatus variable should be used in accordance to installation and removal conventions for conceptual rows. When `vrrpOperationsRowStatus' is set to active(1), no other objects in the conceptual row can be modified. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the Corresponding instance of the `vrrpOperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpOperationsInetAddrType, vrrpOperationsVrId and vrrpOperationsPrimaryIpAddr has been set and there is at least one active row in the `vrrpAssociatedIpAddrTable' defining an associated IP address. notInService(2) should be used to administratively bring the row down. A typical order of operation to add a row is: 1. Create a row in vrrpOperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpAssociatedIpAddrTable. 3. Populate the vrrpOperationsEntry. 4. set vrrpOperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpOperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpAssociatedIpAddrTable to destroy(6) to delete the entry. 3. set vrrpOperationsRowStatus to destroy(6) to delete the entry."
    ],
    null,
    null,
    null,
    null
  ]
}
Records for description 2Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Common and standard MIB copies (LibreNMS/Observium Community), and others1 record · 5 sources

Description 2

vrrpOperationsRowStatus · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), Common and standard MIB copies (LibreNMS/Observium Community), and others5 sources

Status in source: current.

Names: vrrpOperationsRowStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "vrrpOperationsRowStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "RowStatus",
    "MAX-ACCESS",
    "read-create",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The RowStatus variable should be used in accordance to installation and removal conventions for conceptual rows. When `vrrpOperationsRowStatus' is set to active(1), no other objects in the conceptual row can be modified. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the `vrrpOperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpOperationsInetAddrType, vrrpOperationsVrId and vrrpOperationsPrimaryIpAddr has been set and there is at least one active row in the `vrrpAssociatedIpAddrTable' defining an associated IP address. notInService(2) should be used to administratively bring the row down. A typical order of operation to add a row is: 1. Create a row in vrrpOperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpAssociatedIpAddrTable. 3. Populate the vrrpOperationsEntry. 4. set vrrpOperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpOperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpAssociatedIpAddrTable to destroy(6) to delete the entry. 3. set vrrpOperationsRowStatus to destroy(6) to delete the entry.\"",
    "::=",
    "{",
    "vrrpOperationsEntry",
    "14",
    "}"
  ],
  "syntax_tree": [
    [
      "row",
      "RowStatus"
    ],
    null,
    [
      "MaxAccessPart",
      "read-create"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The RowStatus variable should be used in accordance to installation and removal conventions for conceptual rows. When `vrrpOperationsRowStatus' is set to active(1), no other objects in the conceptual row can be modified. To create a row in this table, a manager sets this object to either createAndGo(4) or createAndWait(5). Until instances of all corresponding columns are appropriately configured, the value of the corresponding instance of the `vrrpOperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpOperationsInetAddrType, vrrpOperationsVrId and vrrpOperationsPrimaryIpAddr has been set and there is at least one active row in the `vrrpAssociatedIpAddrTable' defining an associated IP address. notInService(2) should be used to administratively bring the row down. A typical order of operation to add a row is: 1. Create a row in vrrpOperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpAssociatedIpAddrTable. 3. Populate the vrrpOperationsEntry. 4. set vrrpOperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpOperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpAssociatedIpAddrTable to destroy(6) to delete the entry. 3. set vrrpOperationsRowStatus to destroy(6) to delete the entry."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6)

Defense Communication Agency

Current Registration Authority (inferred from ancestor 1.3.6.1.2)

Internet Assigned Numbers Authority

Siblings (13)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.2.1.68.1.7.1.1 vrrpOperationsInetAddrType00
1.3.6.1.2.1.68.1.7.1.2 vrrpOperationsVrId00
1.3.6.1.2.1.68.1.7.1.3 vrrpOperationsVirtualMacAddr00
1.3.6.1.2.1.68.1.7.1.4 vrrpOperationsState00
1.3.6.1.2.1.68.1.7.1.5 vrrpOperationsPriority00
1.3.6.1.2.1.68.1.7.1.6 vrrpOperationsAddrCount00
1.3.6.1.2.1.68.1.7.1.7 vrrpOperationsMasterIpAddr00
1.3.6.1.2.1.68.1.7.1.8 vrrpOperationsPrimaryIpAddr00
1.3.6.1.2.1.68.1.7.1.9 vrrpOperationsAdvInterval00
1.3.6.1.2.1.68.1.7.1.10 vrrpOperationsPreemptMode00
1.3.6.1.2.1.68.1.7.1.11 vrrpOperationsAcceptMode00
1.3.6.1.2.1.68.1.7.1.12 vrrpOperationsUpTime00
1.3.6.1.2.1.68.1.7.1.13 vrrpOperationsStorageType00