POLICY-FRAMEWORK-PIB :: policyCompLimitsType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsPOLICY-FRAMEWORK-PIBpolicyCompLimitsType

policyCompLimitsType

Module: POLICY-FRAMEWORK-PIB

OID (symbolic): POLICY-FRAMEWORK-PIB::policyCompLimitsType

OID (numeric): 1.3.6.1.4.1.45.4.1.1.4.1.3

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: A value describing an implementation limitation for the device related to the PRC or PRC attribute identified by the policyCompLimitsComponent data in this class instance. Values for this object are derived from the defined error values associated with the PRC of the identified attribute or the PRC itself. All genericPrc and specificPrc (defined in a PRC INSTALL-ERRORS clause) error codes represent valid limitation type values.

For example, an implementation of the qosIpAce class may be limited in several ways, such as address mask, protocol and Layer 4 port options. These limitations could be exported using this table with the following instances:

Prid Component Type Guidance 1 'qosIpAceDstAddrMask' 'valueSupLimited' 0xFFFFFFFF 2 'qosIpAceSrcAddrMask' 'valueSupLimited' 0xFFFFFFFF 3 'qosIpAceProtocol' 'valueSupLimited' 0x06 -- TCP 4 'qosIpAceProtocol' 'valueSupLimited' 0x17 -- UDP 5 'qosIpAceDstL4PortMin' 'invalidDstL4PortData' 6 'qosIpAceDstL4PortMax' 'invalidDstL4PortData' 7 'qosIpAcePermit' 'enumSupLimited' 'true'

The above entries describe a number of limitations that may be in effect for the qosIpAce class on a given device. The limitations include restrictions on acceptable values for certain attributes and indications of the relationship between related attributes.

What is policyCompLimitsType?

This read-only value describes an implementation limitation for a PRC or PRC attribute identified by the corresponding policyCompLimitsComponent, using standard error-value codes defined for that PRC. A PDP reads it to understand the specific kind of restriction the device is reporting, such as a value being unsupported or an enumerated option being limited. For example, as the source DESCRIPTION illustrates, a value of 'valueSupLimited' paired with a component of 'qosIpAceProtocol' and a guidance value of 0x06 would tell the PDP that device only supports TCP for that attribute.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.45.4.1.1.4.1.3
snmpwalk -v2c -c public <target> POLICY-FRAMEWORK-PIB::policyCompLimitsType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.45.4.1.1.4.1.3.1
snmpget -v2c -c public <target> POLICY-FRAMEWORK-PIB::policyCompLimitsType.1

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::policyCompLimitsType 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 OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.45synopticsSYNOPTICS-ROOT-MIB
1.3.6.1.4.1.45.4policySYNOPTICS-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.45.4.1policyFrameworkPibPOLICY-FRAMEWORK-PIB
1.3.6.1.4.1.45.4.1.1policyBasePibClassPOLICY-FRAMEWORK-PIB
1.3.6.1.4.1.45.4.1.1.4policyCompLimitsTablePOLICY-FRAMEWORK-PIB
1.3.6.1.4.1.45.4.1.1.4.1policyCompLimitsEntryPOLICY-FRAMEWORK-PIB
1.3.6.1.4.1.45.4.1.1.4.1.3policyCompLimitsTypePOLICY-FRAMEWORK-PIB