RFC1353-MIB :: partySecretsStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsRFC1353-MIBpartySecretsStatus

partySecretsStatus

Module: RFC1353-MIB

OID (symbolic): RFC1353-MIB::partySecretsStatus

OID (numeric): 1.3.6.1.2.1.21.1.1.1.4

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The status of the locally-held information on a particular SNMP party. Setting an instance of this object to the value 'valid(1)' has the effect of ensuring that valid local knowledge exists for the corresponding party. For valid local knowledge to exist, there must be corresponding instances of each object in this table and in the partyTable. Thus, the creation of instances in the partyTable (but not in the aclTable or viewTable) occurs as a direct result of the creation of instances in this table.

Setting an instance of this object to the value 'invalid(2)' has the effect of invalidating all local knowledge of the corresponding party, including the invalidating of any/all entries in the partyTable, the partySecretsTable, the aclTable, and the viewTable which reference said party.

It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive from agents tabular information corresponding to entries not currently in use. Proper interpretation of such entries requires examination of the relevant partySecretsStatus object.

What is partySecretsStatus?

Read-write status controlling whether local knowledge of this party is considered valid: setting valid(1) requires matching entries to exist in both this table and partyTable, and creating a row here also creates the corresponding partyTable row. Setting invalid(2) invalidates every entry referencing this party across the party, secrets, ACL, and view tables at once.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.21.1.1.1.4
snmpwalk -v2c -c public <target> RFC1353-MIB::partySecretsStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.21.1.1.1.4.1
snmpget -v2c -c public <target> RFC1353-MIB::partySecretsStatus.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.2.1.21.1.1.1.4.1 i <value>

Start monitoring vendor-neutral, standards-based MIB, legacy SNMPv2p-capable network devices (obsolete security model) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RFC1353-MIB::partySecretsStatus OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB, legacy SNMPv2p-capable network devices (obsolete security model) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.21snmpSecretsRFC1353-MIB
1.3.6.1.2.1.21.1partyPrivateRFC1353-MIB
1.3.6.1.2.1.21.1.1partySecretsTableRFC1353-MIB
1.3.6.1.2.1.21.1.1.1partySecretsEntryRFC1353-MIB
1.3.6.1.2.1.21.1.1.1.4partySecretsStatusRFC1353-MIB