All MIBs › POLICY-FRAMEWORK-PIB › policyPibIncarnationLongevity
policyPibIncarnationLongevity
Module: POLICY-FRAMEWORK-PIB
OID (symbolic): POLICY-FRAMEWORK-PIB::policyPibIncarnationLongevity
OID (numeric): 1.3.6.1.4.1.45.4.1.1.2.1.4
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: This attribute controls what the PEP does with the downloaded policy on receipt of a Client Close message or a loss of connection to the PDP.
If set to expireNever, the PEP continues to operate with the installed policy indefinitely. If set to expireImmediate, the PEP immediately expires the policy obtained from the PDP and installs policy from local configuration. If set to expireOnTimeout, the PEP continues to operate with the policy installed by the PDP for a period of time specified by policyPibIncarnationTtl. After this time (and it has not reconnected to the original or new PDP) the PEP expires this policy and reverts to local configuration.
For all cases, it is the responsibility of the PDP to check the incarnation and download new policy, if necessary, on a reconnect.
Policy enforcement timing only applies to policies that have been installed dynamically (e.g., by a PDP via COPS).
What is policyPibIncarnationLongevity?
This read-write value controls what the device (PEP) does with its downloaded policy if it receives a Client Close message or loses its connection to the PDP: expireNever keeps running the installed policy indefinitely, expireImmediate reverts immediately to local configuration, and expireOnTimeout keeps the PDP-installed policy for a grace period before falling back. An admin sets it to control the device's fail-safe behavior during a PDP outage, balancing continued policy enforcement against the risk of running stale policy for too long. For example, an admin might set this to expireOnTimeout so the device keeps enforcing current QoS policy for a short grace period during a brief PDP outage, rather than immediately reverting to a less specific local configuration.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.4.1.1.2.1.4 snmpwalk -v2c -c public <target> POLICY-FRAMEWORK-PIB::policyPibIncarnationLongevity
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.45.4.1.1.2.1.4.1 snmpget -v2c -c public <target> POLICY-FRAMEWORK-PIB::policyPibIncarnationLongevity.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.45.4.1.1.2.1.4.1 i <value>
Start monitoring vendor-neutral, standards-based MIB (IETF RAP Policy Framework PIB, COPS-PR) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the POLICY-FRAMEWORK-PIB::policyPibIncarnationLongevity OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB (IETF RAP Policy Framework PIB, COPS-PR) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.45 | synoptics | SYNOPTICS-ROOT-MIB |
| 1.3.6.1.4.1.45.4 | policy | SYNOPTICS-ROOT-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.45.4.1 | policyFrameworkPib | POLICY-FRAMEWORK-PIB |
| 1.3.6.1.4.1.45.4.1.1 | policyBasePibClass | POLICY-FRAMEWORK-PIB |
| 1.3.6.1.4.1.45.4.1.1.2 | policyPibIncarnationTable | POLICY-FRAMEWORK-PIB |
| 1.3.6.1.4.1.45.4.1.1.2.1 | policyPibIncarnationEntry | POLICY-FRAMEWORK-PIB |
| 1.3.6.1.4.1.45.4.1.1.2.1.4 | policyPibIncarnationLongevity | POLICY-FRAMEWORK-PIB |