Status in source: current.
Names: vrrpv3OperationsRowStatus
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vrrpv3OperationsRowStatus",
"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 `vrrpv3OperationsRowStatus' 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 `vrrpv3OperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpv3OperationsInetAddrType, vrrpv3OperationsVrId and vrrpv3OperationsPrimaryIpAddr has been set and there is at least one active row in the `vrrpv3AssociatedIpAddrTable' 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 vrrpv3OperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpv3AssociatedIpAddrTable. 3. Populate the vrrpv3OperationsEntry. 4. set vrrpv3OperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpv3OperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpv3AssociatedIpAddrTable to destroy(6) to delete the entry. 3. set vrrpv3OperationsRowStatus to destroy(6) to delete the entry.\"",
"::=",
"{",
"vrrpv3OperationsEntry",
"13",
"}"
],
"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 `vrrpv3OperationsRowStatus' 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 `vrrpv3OperationsRowStatus' column will be read as notReady(3). In particular, a newly created row cannot be made active(1) until (minimally) the corresponding instance of vrrpv3OperationsInetAddrType, vrrpv3OperationsVrId and vrrpv3OperationsPrimaryIpAddr has been set and there is at least one active row in the `vrrpv3AssociatedIpAddrTable' 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 vrrpv3OperationsTable with createAndWait(5). 2. Create one or more corresponding rows in vrrpv3AssociatedIpAddrTable. 3. Populate the vrrpv3OperationsEntry. 4. set vrrpv3OperationsRowStatus to active(1). A typical order of operation to delete an entry is: 1. Set vrrpv3OperationsRowStatus to notInService(2). 2. Set the corresponding rows in vrrpv3AssociatedIpAddrTable to destroy(6) to delete the entry. 3. set vrrpv3OperationsRowStatus to destroy(6) to delete the entry."
],
null,
null,
null,
null
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: CISCOSB-VRRPV3-MIB
See published definition above
Module imports
{'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'MacAddress', 'TruthValue', 'TimeStamp', 'TimeInterval'], 'CISCOSB-IP': ['ipSpec'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Counter32', 'Integer32', 'mib-2', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}
Related source files and packages:
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: VRRPV3-MIB
Same published definition
Module imports
{'IF-MIB': ['ifIndex'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'MacAddress', 'TruthValue', 'TimeStamp', 'TimeInterval'], 'CISCOSB-IP': ['ipSpec'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Counter32', 'Integer32', 'mib-2', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}
- NETGEAR official product and EOL MIB downloads
· Publisher's source file: Source package: MS510TX_TXPP_MIBS_V6.7.0.43.zip
Module: VRRPV3-MIB
See published definition above
Module imports
{'IF-MIB': ['ifIndex'], 'RADLAN-IP': ['ipSpec'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'MacAddress', 'TruthValue', 'TimeStamp', 'TimeInterval'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Counter32', 'Integer32', 'mib-2', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress']}
Related source files and packages:
Same file in MX510TX_MS510TXPP_MIBS_ODM_V6.7.0.42.zip.
Same file in MS510TX_TXPP_V6.7.0.37_MIB_V6.7.0.37.zip.