CISCO-PFR-MIB: View SNMP OID List / Download MIB

This MIB module defines objects that describe Performance Routing (PfR). Standard routing protocols base routing decisions on reachability and the number of hops between the source and destination networks. PfR collects and analyzes other performance data, such as delay, loss, jitter, MOS, and link utilization, which allows it to make routing decisions based on policies defined by the network administrator. Glossary ======== PfR Performance Routing. MC PfR Master Controller. BR PfR Border Router. DRIP Dynamic Router Interaction Protocol. TC PfR Traffic Class. IPSLA IP Service Level Agreement (active probing). Exit PfR external interface. Link Group PfR logical grouping of exits to narrow down potential exits for a TC to use. Cost Minimization PfR feature that assigns costs to exits and minimizes the overall monetary cost for a TC Rollup Data collection for monetary cost calculation for all available exits. DSCP Diff-Serv Control Point. PfR Policy Global PfR policy defined under PfR master. TC policy defined under PfR map. PfR Map Container for a PfR policy. MOS Mean opinion score PBR Policy based routing. PBR uses route map to enforce the routing decision made by PfR. PfR Elements ============ A PfR system consists of a Master Controller (MC) and one or more Border Routers (BRs). The MC is a hardware or software entity that is not in the data path. A BR is a software entity in the data path, typically running on an edge router. The MC and BRs communicate with each other over a socket interface using the Dynamic Router Interaction Protocol (DRIP). The MC sends commands to the BRs related to PfR Policies and the monitoring of PfR traffic classes (TCs). The BRs send performance data gathered using either 'passive data' provided by NetFlow, 'active data' provided by sending artificial probes that are created using IPSLA APIs, or both, depending on the PfR policies configured on the MC. This MIB module describes a MC object as a single row in the cpfrMCTable and the BR object as a single row in the cpfrBRTable. PfR Exits ========= A PfR system must have at least two interfaces (i.e., exits) configured as 'external interfaces' over which a TC's destination network is reachable in order for PfR to function. These two exits can be on the same BR or on different BRs. +------+ +------+ |----> Exit 1 | MC | ---- | BR | ---- | +------+ +------+ |----> Exit 2 **** OR **** +------+ | ---- | BR | ----> Exit 1 +------+ | +------+ | MC | ---- | +------+ | +------+ | ---- | BR | ----> Exit 2 +------+ PfR can assign these exits to different PfR Link Groups. A PfR exit can be in at most three Link Groups at one time. (See 'PfR Policies' below). This MIB module describes a PfR exit as a single row in the cpfrExitTable and a cost minimization policy of an exit as a single row of the cpfrExitCostTierTable. PfR Traffic Classes =================== A traffic class is a generic term for a set of traffic flows coming into or going out of a network that have a common characteristic, such as destination address, source address, application, or DSCP value. The simplest form of a TC is 'all traffic going to the same destination prefix'. Additional parameters defines more specific TCs. PfR monitors the TCs that are specified either by enabling PfR learn mode or by direct configuration in a PfR map. PfR can learn TCs with the highest throughput, with the highest delay, with a destination address inside the PfR network, or TCs that matches a configured PfR Learn List. The BRs use iBGP to obtain information about 'inside TCs'. A PfR map specifies TCs to which the policy applies by configuring match clause. This MIB module describes a PfR TC as a single row in the cpfrTrafficClassTable and current status of a TC as a single row of the cpfrTrafficClassStatusTable, and performance metrics gathered for a specific TC as a single row of the cpfrTrafficClassMetricsTable. PfR Policies ============ A PfR policy describes the performance metrics the router is to gather, how to gather these metrics, how frequently it should gather these metrics, and how these metrics influence routing decisions. Once enabled, PfR provides a global default PfR policy. A PfR policy can be configured to use one link group as a 'primary' and one as a 'fallback' link group. If PfR determines that a TC has gone 'Out of Policy' based on the current PfR policy, it attempts to move the TC to an exit in the same primary link group, and only moves it to an exit in the fallback link group, if configured, if no exit in the primary link group is 'In Policy'. This MIB module describes a PfR map policy in a single row of the cpfrMapTable and a match clause configured for a specific PfR map as a single row of the cpfrMatchTable.

The device generates this notification when one of cpfrMCLoggingAdminStatus, cpfrMCAdminStatus, cpfrMCControlMode, cpfrMCClear, on PfR master controller is changed.

The device generates this notification when the master controller detects a status change with a border router.

The device generates this notification when the master controller detects a status change with an exit link.

The device generates this notification when the master controller detects a traffic class status event.

The device generates this notification, when the master controller detects number of in-policy traffic class falls below the configured threshold.

The device generates this notification, when the master controller detects number of in-policy traffic classes at primary link group falls below the configured threshold.

This table lists the MC instances created by the system.

An entry describing the configuration and status of one PfR MC. A simple device may only support a single MC, where a more sophisticate device may support more than one MC. A peer SNMP entity may create a MC by setting an instance of cpfrMCRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a MC. In these cases, the system must automatically create a row in the cpfrMCTable. A peer SNMP entity may destroy a MC by setting the corresponding instance of cpfrMCRowStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a MC. In these cases, the system must automatically destroy the corresponding row in the cpfrMCTable.

This object indicates an arbitrary integer-value that uniquely identifies a PfR MC.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): cpfrMCMapIndex, cpfrMCKeepAliveTimer, cpfrMCMaxPrefixTotal, cpfrMCMaxPrefixLearn, cpfrMCMaxRangeReceivePercent, cpfrMCMaxRangeUtilPercentMax, cpfrMCPortNumber, cpfrMCTracerouteProbeDelay, cpfrMCRsvpPostDialDelay, cpfrMCRsvpSignalingRetries, cpfrMCNetflowExporter, cpfrMCAdminStatus.

This object specifies the status of a row in the MC table. The following columnar objects must be valid in order to transition the row to the active state: None. The following columnar objects can be modified when the row is in the active state: None

This object indicates a set of PfR policy map entries in cpfrMapTable associated with the MC. A value of zero indicates that there is no policy map associated with the MC and that the values in the default policy should be used for all TCs. The peer SNMP entity can retrieve this value and retrieve the cpfrMapEntry rows indexed by this value to understand the PfR policies. Alternatively the peer SNMP entity can assign the value of pfrMapIndex to this object to associate a set of policies to MC.

This object specifies the value of the PfR keepalive timer. The MC sends keepalive packets to BRs to maintain connectivity between the MC and the BR. If the MC does not receive keepalive packets from a BR before the keepalive timer expires and this situation happens three times in a row, then the MC will not maintain the connection.

This object specifies the maximum number of prefixes that a PfR MC will monitor. Limiting the number of prefixes a MC will monitor and learn reduces memory and system resource consumption.

This object specifies the maximum number of prefixes that a PfR MC will learn.

This object specifies the maximum utilization threshold of incoming traffic that can be transmitted over a PfR-managed entrance link interface.

This object specifies the maximum utilization of outbound traffic that can be transmitted over a PfR-managed exit interface.

This object specifies a dynamic port number for communication between a PfR MC and a PfR BR.

This object specifies the time interval between traceroute probe cycles.

This object specifies the delay before PfR returns the default routing path to RSVP.

This object specifies the number of retries that RSVP will query PfR for the alternate path.

This object specifies the name of PfR Netflow exporter.

This object can be used to enable or disable PfR operation in the system. 'enable' Enable MC on the router. 'disable' Disable MC on the router. Enumeration: 'enable': 1, 'disable': 2.

This object indicates the operational status of PfR MC. 'active' MC is active. 'inactive' MC is not active. Enumeration: 'active': 1, 'inactive': 2.

This object indicates the state of the connection between MC and BRs. 'success' MC is successfully connected to at least one BR. 'closed' MC is not connected to any BR. Enumeration: 'closed': 2, 'success': 1.

This object indicates the number of BRs that peer with the MC.

This object indicates the total number of PfR external interfaces configured on a MC.

This object indicates the status of PfR learning operation. 'disable' PfR learning mode is not enabled. 'started' PfR is learning TCs. 'writing' PfR is storing the learned data of TCs. 'sleep' PfR is waiting for entering into another learning period. 'retry' PfR is retrying to learn the TCs. Enumeration: 'disabled': 1, 'started': 2, 'retry': 5, 'sleep': 4, 'writing': 3.

This object indicates time remaining in the current prefix learning period measured in seconds.

This object indicates the total number of prefixes PfR is monitoring.

This object indicates the number of prefixes PfR has learned.

This object indicates the number of configured prefixes PfR is monitoring.

This object indicates whether the PBR requirements have been met. If PBR requirements are not met, the BRs cannot communicate with each other over the internal interfaces and cannot redirect traffic to each other using PBR route maps.

This object specifies whether logging is enabled or not on PfR MC. 'enable' logging is enabled. 'disable' logging is disabled. Enumeration: 'enable': 1, 'disable': 2.

This object specifies PfR MC control-mode. 'observe' PfR doesn't control traffic classes, but observes them. 'control' PfR controls traffic classes. Enumeration: 'control': 2, 'observe': 1.

This object specifies the clear operation that an MC should perform. A read on this object will return the last successful clear operation performed by the master controller. 'none' No clear operation was executed by MC since the time it became operational. This is read-only. 'clearAll' Specifies the MC to clear all prefixes in PfR master database, connections to all border routers, and restart the PfR master process. 'clearAllPrefixes' Specifies the MC to clear all prefixes in PfR master database. 'clearAllBorders' Specifies the MC to clear connections to all border routers. Enumeration: 'clearAllPrefixes': 3, 'none': 1, 'clearAll': 2, 'clearAllBorders': 4.

This object indicates the value of sysUpTime the last time the MC successfully performed a clear operation.

This object specifies whether PfR notifications is enabled or not from PfR MC. 'enable' notification is enabled. 'disable' notification is disabled. Enumeration: 'enable': 1, 'disable': 2.

This object indicates which of the following configuration is changed. 'cpfrMCLoggingAdminStatus' cpfrMCLoggingAdminStatus is changed. 'cpfrMCAdminStatus' cpfrMCAdminStatus is changed. 'cpfrMCControlMode' cpfrMCControlMode is changed. 'cpfrMCClear' cpfrMCClear is changed. Enumeration: 'cpfrMCControlMode': 3, 'cpfrMCAdminStatus': 2, 'cpfrMCLoggingAdminStatus': 1, 'cpfrMCClear': 4.

This object indicates the value to which the type of configuration specified in cpfrMCChangeConfigType, is changed.

This table lists the PfR map instances created by the system. This table has a sparse expansion dependent relationship on cpfrMCTable, containing one or more rows for each cpfrMCEntry.

An entry describing the configuration of one PfR map. A device creates a row in a cpfrMapTable when it specifies a PfR map. Likewise, such a device destroys a row in the cpfrBRTable when removing a PfR map. A peer SNMP entity may create a PfR map by setting an instance of cpfrMapRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a PfR Map. In these cases, the system must automatically create a row in the cpfrMapTable. A peer SNMP entity may destroy a PfR map by setting the corresponding instance of cpfrMapRowStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a Map. In these cases, the system must automatically destroy the corresponding row in the cpfrMapTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrMCEntry.

This object indicates an arbitrary integer-value that uniquely identifies a set of PfR policy maps.

This object indicates an arbitrary integer-value that, in combination with cpfrMapIndex, uniquely identifies a PfR policy map.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): cpfrMapIndex, cpfrMapPolicyIndex, cpfrMapStorageType, cpfrMapRowStatus, cpfrMapName, cpfrMapBackoffMinTimer, cpfrMapBackoffMaxTimer, cpfrMapBackoffStepTimer, cpfrMapDelayType, cpfrMapDelayRelativePercent, cpfrMapDelayThresholdMax, cpfrMapHolddownTimer, cpfrMapPrefixForwardInterface, cpfrMapJitterThresholdMax, cpfrMapLinkGroupName, cpfrMapFallbackLinkGroupName, cpfrMapLossType, cpfrMapLossRelativeAvg, cpfrMapLossThresholdMax, cpfrMapModeMonitor, cpfrMapModeRouteOpts,cpfrMapRouteMetricBgpLocalPref, cpfrMapRouteMetricEigrpTagCommunity, cpfrMapRouteMetricStaticTag, cpfrMapModeSelectExitType, cpfrMapMossThresholdMin, cpfrMapMossPercentage, cpfrMapNextHopAddressType, cpfrMapNextHopAddress, cpfrMapPeriodicTimer, cpfrMapActiveProbeFrequency, cpfrMapActiveProbePackets, cpfrMapTracerouteReporting, cpfrMapUnreachableType, cpfrMapUnreachableRelativeAvg, cpfrMapUnreachableThresholdMax, cpfrMapRoundRobinResolver.

This object specifies the status of a row in the PfR map table. The following columnar objects must be valid in order to transition the row to the active state: cpfrMapName. The following columnar objects can be modified when the row is in the active state: None

This object specifies the name of a PfR map.

This object specifies the minimum value for the backoff timer. The backoff timer is used to configure a PfR map to set the transition period for which the MC holds an out-of-policy prefix.

This object specifies the maximum value for the backoff timer. If the maximum timer expires and all PfR-managed exits are out-of-policy, PfR will install the best available exit and reset the minimum timer.

This object specifies the time period value for the step timer. PfR users the step timer to add time to the out-of-policy waiting period each time the backoff timer expires and PfR is unable to find an in-policy exit. The backoff timer is initialized to the minimum timer and incremented by the step timer until it reaches the maximum timer.

This object specifies the delay type of a PfR map. It is used to set the delay threshold as a relative percentage or as an absolute value for match criteria.

This object specifies a relative delay threshold based on a comparison of short-term and long-term delay percentages. The value of this object is valid if the corresponding value of cpfrMapDelayType is set to 'relative'.

This object specifies the absolute maximum delay time. The value of this object is valid if the corresponding value of cpfrMapDelayType is set to 'threshold'.

This object specifies the route dampening time period. It is used to configure the prefix route dampening timer for the minimum period of time in which a new exit must be used before an alternate exit can be selected.

This object specifies whether or not a null forwarding interface has been configured. This interface is always up and can never forward or receive traffic; encapsulation always fails. Null interfaces are used as a low-overhead method of discarding unnecessary network traffic.

This object specifies the maximum tolerable jitter value permitted on an exit link.

This object specifies the primary link group to be used by PfR to select an exit. It allows a group of exit links to be defined as a preferred set of links for PfR to use when optimizing TCs specified in a PfR policy.

This object specifies a fallback link group to be used if all the exits in the primary link group are out-of-policy (OOP).

This object specifies the loss type configuration used by PfR. It specifies the relative percentage or maximum number of packets that PfR will permit to be lost during transmission on an exit link.

This object specifies a relative percentage of packet loss based on a comparison of short-term and long-term packet loss percentages. The value of this object is valid if the corresponding value of cpfrMapLossType is set to 'relative'.

This object specifies absolute packet loss based on packets per million (PPM). The value of this object is valid if the corresponding value of cpfrMapLossType is set to 'threshold'.

This object specifies how a PfR MC using this PfR map should monitor the TCs. 'active' Enable active monitoring. 'activethrougput' Enable active monitoring with throughput data from passive monitoring. 'both' Enable both active and passive monitoring. 'fast' Enable continuous active and passive monitoring. 'passive' Enable passive monitoring. Enumeration: 'active': 1, 'activeThroughput': 2, 'passive': 5, 'fast': 4, 'both': 3.

This object specifies how a PfR MC using this PfR map should control the TCs. 'control' Monitor and report performance data and use the data to make route changes that will optimize performance. 'observe' Monitor and report performance data without making any route changes. 'metric' Enable route control based on BGP Local preference, EIGRP community tag, or a specific static route tag. Enumeration: 'control': 1, 'metric': 3, 'observe': 2.

This object specifies the BGP local preference for PfR controlled routes. The value of this object is valid if the corresponding value of cpfrMapModeRouteOpts is set to 'metric'. The value 0 is not a valid BGP local preference. Configuring 0 disables route control based on BGP local preference.

This object specifies the community value to an EIGRP route under PfR control. The value of this object is valid if the corresponding value of cpfrMapModeRouteOpts is set to 'metric'. The value 0 is not a valid EIGRP Community tag. Configuring 0 disables route control based on EIGRP.

This object specifies the tag to a static route under PfR control. The value of this object is valid if the corresponding value of cpfrMapModeRouteOpts is set to 'metric'. The value 0 is not a valid Static tag. Configuring 0 disables route control based on static tag.

This object specifies how a PfR MC using this PfR map should select an exit based on performance or policy. 'best' Select the best exit based on performance or policy. 'good' Select the first exit that is in policy. Enumeration: 'good': 2, 'best': 1.

This object specifies a threshold MOS value that represents a minimum voice quality for exit link utilization.

This object specifies a percentage value that is compared with the percentage of MOS samples that are below the MOS threshold. The number of MOS samples over a period of time that are below the threshold MOS value are calculated. If the percentage of MOS samples below the threshold is greater than the configured percentage, PfR determines that the exit link is out-of-policy and searches for an alternate exit link.

This object specifies the address type of the address specified as the next hop when PfR is used for sinkhole filtering.

This object specifies the next hop address to which PfR forwards packets for matching prefixes. The prefixes that are forwarded to the next hop address are specified by an access list configured in a match clause on the PfR map

This object specifies the periodic timer that PfR uses to select the best exit for the matched TCs. When this timer expires, PfR automatically selects the best exit, irrespective of whether the current exit is in-policy or out-of-policy. The periodic timer is reset when the new exit is selected.

This object specifies the frequency of active probes configured under a PfR map.

This object specifies the number of probe packets generated for each active probe cycle.

This object enables continuous and policy-based traceroute probing. Traceroute probing allows prefix performance to be measured on a hop-by-hop basis. Delay, loss, and reachability measurements are gathered for each hop from the probe source to the target prefix. 'none' Traceroute probing is disabled. 'delay' Delay policy based traceroute probing is enabled. 'loss' Loss policy based traceroute probing is enabled. 'reachability' Reachability policy based traceroute probing is enabled. Bits: 'delay': 1, 'loss': 2, 'none': 0, 'unreachable': 3.

This object specifies the unreachable type configuration used by PfR. It is used to set the relative percentage or the absolute maximum number of unreachable hosts, based on flows per million (fpm), that PfR will permit from a PfR-managed exit link.

This object specifies a relative percentage of unreachable hosts. The relative unreachable host percentage is based on a comparison of short-term and long-term measurements. The short-term measurement reflects the percentage of hosts that are unreachable within a 5-minute period. The long-term measurement reflects the percentage of unreachable hosts within a 60-minute period. The following formula is used to calculate this value: Relative percentage of unreachable hosts equals to the difference between short-term percentage and long-term percentage divided by long-term percentage. The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the exit link is determined to be out-of-policy. The value of this object is valid if the corresponding value of cpfrMapUnreachableType is set to 'relative'.

This object specifies the absolute maximum number of unreachable hosts based on flows per million. The value of this object is valid if the corresponding value of cpfrMapUnreachableType is set to 'threshold'.

This object specifies whether the round robin resolver is enabled or disabled. 'enable' Round robin resolver is enabled. 'disable' Round robin resolver is disabled. Enumeration: 'enable': 1, 'disable': 2.

This object specifies the event notification control type configuration used by PfR. It is used to set the relative percentage or the absolute threshold value for cpfrMapEventNotifCtrlThreshold object.

This object specifies the absolute event counter threshold or relative percentage threshold used by PfR to throttle the generation of cpfrTCInpolicyThresholdBelowNotify and cpfrTCPrimaryThresholdBelowNotify. If the value is relative percentage threshold, then the notification is generated if cpfrMapEventTCCount over total TC count is more than the value of this percentage. - If the value is absolute event counter threshold, then the notification is generated if cpfrEventTrapTCCount is more than this value.

This object specifies the current absolute number of traffic classes, whose state are 'default' or 'oopolicy' specified by cpfrTCStatus.

This table lists the match clause instances created by the system. This table has an expansion dependent relationship on cpfrMapTable, containing zero or more rows for each cpfrMapEntry.

An entry describing a match clause PfR uses. A peer SNMP entity may create a match criterion by setting an instance of cpfrMatchStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a match criterion. In these cases, the system must automatically create a row in the cpfrMatchTable. A peer SNMP entity may destroy a match criterion by setting the corresponding instance of cpfrMatchStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a match criterion. In these cases, the system must automatically destroy the corresponding row in the cpfrMatchTable. The system automatically destroys a row when the system or EMS/NMS destroys the corresponding entries in the cpfrMapTable.

This object specifies which of those objects are valid. When a user is configuring a match clause, the corresponding bit should also be set to true in this object. The following list shows different types of match clauses, the bit to be set and the corresponding objects. 'access-list' If this bit is set to '1' then corresponding instance of cpfrMatchAccessList is valid. 'prefix-list' If this bit is set to '1' then corresponding instance of cpfrMatchPrefixList is valid. 'inside' If this bit is set to '1' then corresponding instance of cpfrMatchInside is valid. 'learn' If this bit is set to '1' then corresponding instances of cpfrMatchLearnMode and cpfrMatchLearnListName are valid. 'nbarApplicationList' If this bit is set to '1' then corresponding instance of cpfrMatchTCNbarListName is valid. Bits: 'nbarApplicationList': 4, 'trafficClassPfx': 5, 'trafficClassACL': 3, 'accessList': 0, 'prefixList': 1, 'learn': 2.

This object specifies the access list used to manually configure a traffic class that matches destination prefixes in an access list used in a PfR map.

This object specifies the prefix list used to manually configure a traffic class that matches destination prefixes in a prefix list.

This object specifies whether or not the prefixes learned by PfR are within the internal network.

This object specifies the mode by which PfR should learn prefixes. 'Delay' PfR learns prefixes based on the highest delay. 'Inside' PfR learns the prefixes inside the network. 'Throughput' PfR learns prefixes based on the highest throughput. 'list' PfR learns prefixes based on a learn list. Enumeration: 'delay': 1, 'list': 4, 'inside': 2, 'throughput': 3.

This object specifies the learn list name used by PfR for learning prefixes. This object is valid when the corresponding cpfrMatchLearnMode object is set to 'list'.

This object specifies that PfR is to profile traffic destined for prefixes defined in an IP prefix list that match one or more NBAR applications. The applications are predefined with a protocol identifier. This object identifies a set of protocols in cpfrNbarApplListTable.

This object specifies the prefix list to be used by PfR to filter traffic that is learned based on NBAR applications.

This object specifies whether or not the prefixes filtered by the prefix list is inside the internal network.

This table lists the resolver instances created by the system. This table has an expansion dependent relationship on cpfrMapTable, containing zero or more rows for each cpfrMapEntry.

An entry in the cpfrResolveTable describes a policy metric and its priority relative to other metrics if multiple metrics are configured for the default policy or under a PfR map. A peer SNMP entity may create a resolver by setting an instance of cpfrResolveRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a resolver. In these cases, the system must automatically create a row in the cpfrResolveTable. A peer SNMP entity may destroy a resolver by setting the corresponding instance of cpfrResolveRowStatus to 'destroy'. Observe that an mplementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a resolver. In these cases, the system must automatically destroy the corresponding row in the cpfrResolveTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrMapTable.

This object indicates an arbitrary integer-value that uniquely identifies a PfR resolver.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): cpfrResolvePolicyType, cpfrResolveVariance, cpfrResolveMapIndex, cpfrResolveMapIndex.

This object specifies the status of a row in the resolver table. The following columnar objects must be valid in order to transition the row to the active state: cpfrMCResolvePriority, cpfrResolvePolicyType, cpfrResolveMapIndex, cpfrResolveMapPolicyIndex The following columnar objects can be modified when the row is in the active state: None

This object indicates the priority of the resolver.

This object indicates the type of this resolver policy.

This object specifies the allowable variance for the policy, as a percentage.

This object refers to the map Index of PfR map under which this resolver was configured.

This object refers to PfR map policy index of PfR map under which this resolver was configured.

This table lists the PfR learn instances created by the system. This table has a one-to-one relationship with cpfrMCTable, containing zero or more rows for each cpfrMCEntry.

An entry in the cpfrLearnTable describes the configuration and status of a PfR learning policy. A device creates a row in a cpfrLearnTable when PfR learn is enabled. Likewise, such a device destroys a row in the cpfrLearnTable when PfR learn is disabled.

This object specifies how a MC aggregates learned prefixes based on traffic type. 'bgp' The bgp keyword configures aggregation based on entries in the BGP routing table. 'nonBgp' The non-bgp keyword configures aggregation based on static routes. 'prefixLength' The prefix-length keyword configures aggregation based on the specified prefix length. The range of values that can be configured for this argument is a prefix mask from 1 to 32. If this command is not specified, the default aggregation is performed based on a /24 prefix length Enumeration: 'bgp': 1, 'nonBgp': 2, 'prefixLength': 3.

This object configures aggregation based on the specified prefix length.

This object specifies the method by which PfR learns prefixes. 'delay' Learn prefixes with the highest round trip delay. 'throughput' Learn prefixes with the highest throughput. 'insideBgp' Learn prefixes inside the network. Bits: 'delay': 0, 'throughput': 1, 'insideBgp': 2.

This object specifies the length of time that the learned prefixes are kept in the central policy database. 'session' Configures a session-based expiration timer. 'time' Configures a time-based expiration timer. Enumeration: 'session': 1, 'time': 2.

This object configures a session-based expiration timer. A number from 1 to 65535 can be entered. Each increment represents one monitoring period. The object is valid when cpfrLearnExpireType is configured with session.

This object configures a time-based expiration timer.

This object specifies the time period over which a PfR MC learns traffic flows.

This object specifies the time interval between prefix monitoring periods.

This object specifies the maximum number of prefixes PfR can learn.

This object specifies a PfR access list to define criteria which PfR uses to aggregate TCs.

This object specifies an access list used to filter TCs learned by PfR.

This table lists the learn lists created by the system. This table has an expansion dependent relationship on cpfrLearnTable, containing zero or more rows for each cpfrLearnEntry.

An entry in the cpfrLearnListTable describes the configuration and status of a PfR learn list. A peer SNMP entity may create a learn list by setting an instance of cpfrLearnListRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a learn list. In these cases, the system must automatically create a row in the cpfrLearnListTable. A peer SNMP entity may destroy a learn list by setting the corresponding instance of cpfrLearnListRowStatus to 'destroy'. Observe that an mplementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a learn list. In these cases, the system must automatically destroy the corresponding row in the cpfrLearnListTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrLearnTable.

This object indicates an arbitrary integer-value that uniquely identifies a PfR learn list.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): cpfrLearnListReferenceName, cpfrLearnListSequenceNum, cpfrLearnListMethod, cpfrLearnListDelayType, cpfrLearnListDelayRelativePercentage, cpfrLearnListDelayThresholdMax, cpfrLearnListAclName, cpfrLearnListFilterPfxName, cpfrLearnListPfxName, cpfrLearnListPfxInside, cpfrLearnListNbarAppl.

This object specifies the status of a row in the learn list table. The following columnar objects must be valid in order to transition the row to the active state: cpfrLearnListReferenceName, cpfrLearnListSequenceNum. The following columnar objects can be modified when the row is in the active state: None

This object specifies the reference name of a learn list.

This object specifies the sequence number representing a sequence that is used to determine the order in which PfR applies learn list criteria.

This object specifies how PfR learns prefixes. 'delay' Learn prefixes with the highest round trip delay. 'througput' Learn prefixes with the highest throughput. 'rsvp' Learn prefixes on the basis of RSVP. Bits: 'delay': 0, 'throughput': 1, 'rsvp': 2.

This object specifies the name of the access list to be used by the PfR learn list.

This object specifies the name of the prefix list to be used by the PfR learn list.

This object specifies whether PfR should learn prefixes that are inside the network.

This object specifies a set of protocols in the cpfrNbarApplListTable that will be used by PfR to learn TCs.

This object specifies the name of the prefix list to be used as a filter for traffic classes to be learned by this learn list.

This table lists the active probe instances created by the system. This table has an expansion dependent relationship on cpfrMapTable, containing zero or more rows for each cpfrMapEntry.

An entry in the cpfrActiveProbeTable describes the configuration and status that directs how PfR active-probes targets. A peer SNMP entity may create an active probe by setting an instance of cpfrActiveProbeRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create an active probe. In these cases, the system must automatically create a row in the cpfrActiveProbeTable. A peer SNMP entity may destroy an active probe by setting the corresponding instance of cpfrActiveProbeRowStatus to 'destroy'. Observe that an mplementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy an active probe. In these cases, the system must automatically destroy the corresponding row in the cpfrActiveProbeTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrMapTable.

This object indicates an arbitrary integer-value that uniquely identifies an active probe entity in a PfR policy map.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): pfrActiveProbeType, cpfrActiveProbeTargetAddressType, cpfrActiveProbeTargetAddress, cpfrActiveProbeTargetPortNumber, cpfrActiveProbePfrMapIndex, cpfrActiveProbeDscpValue, cpfrActiveProbeCodecName, cpfrActiveProbeMapIndex, cpfrActiveProbeMapPolicyIndex, cpfrActiveProbeAdminStatus.

This object specifies the status of row in the active probe table. The following columnar objects must be valid in order to transition the row to the active state: cpfrActiveProbeType, cpfrActiveProbeTargetAddressType, cpfrActiveProbeTargetAddress, cpfrActiveProbeTargetPortNumber, cpfrActiveProbeMapIndex, cpfrActiveProbeMapPolicyIndex. The following columnar objects can be modified when the row is in the active state: None

This object specifies the Type of probe. 'echo' Use Internet Control Message Protocol (ICMP) echo messages (ping) for active probe. 'jitter' Use jitter messages for active probe. 'tcp-conn' Use TCP connection messages for active probe. 'udp-echo' Use User Datagram Protocol (UDP) echo messages for active probe. Enumeration: 'udpEcho': 4, 'tcpConn': 3, 'jitter': 2, 'echo': 1.

This object specifies the type of a target IP address of a prefix to be monitored using the specified type of probe.

This object specifies target IP address of a prefix to be monitored using the specified type of probe.

This object specifies the destination port number for the active probe.

This object specifies the index of the PfR policy map on which the active probe clause is configured.

This object indicates the Differentiated Services Code Point (DSCP) value.

This object specifies the codec value used for Mean Opinion Score (MOS) calculation and only used with the jitter probe type. The codec values must be one of the following, 'g711alaw' G.711 A Law 64000 bps. 'g711ulaw' G.711 U Law 64000 bps. 'g729a' G.729 8000 bps. Enumeration: 'g729a': 3, 'g711ulaw': 2, 'g711alaw': 1.

This object specifies the index of a PfR map under which this active probe was configured.

This object specifies the index of a PfR map policy under which this active probe was configured.

This object specifies whether the probe is assigned to a prefix or not, or is a forced probe configured on a PfR map. 'assigned' Active probe is assigned. 'unassigned' Active probe is unassigned. 'forced' Active probe is sent to forced targets configured in PfR map. Enumeration: 'assigned': 1, 'forced': 3, 'unassigned': 2.

This object indicates the current status of an active probe. 'running' Active probe is running. 'notrunning' Active probe is not running. Enumeration: 'running': 1, 'notRunning': 2.

This object indicates the type of assigned prefix address.

This object indicates the assigned prefix address.

This object indicates the length of the assigned prefix address.

This object indicates how an active probe is entered into the PfR system. 'learned' Active probe is triggered when PfR learns TCs. 'configured' Active probe is forced by CLI command. Enumeration: 'learned': 1, 'configured': 2.

This table lists the border router (BR) instances created by the system. This table has an expansion dependent relationship on the cpfrMCTable, containing zero or more rows for each cpfrMCEntry.

An entry in the cpfrBRTable describes the configuration and status of one PfR BR. A peer SNMP entity may create a BR by setting an instance of cpfrBRRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create an exit. In these cases, the system must automatically create a row in the cpfrBRTable. A peer SNMP entity may destroy a BR by setting the corresponding instance of cpfrBRRowStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a BR. In these cases, the system must automatically destroy the corresponding row in the cpfrBRTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrMCEntry.

This object indicates an arbitrary integer-value that uniquely identifies a PfR BR.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): cpfrBRAddressType, cpfrBRAddress, cpfrBRKeyName.

This object specifies the status of a row in the BR table. The following columnar objects must be valid in order to transition the row to the active state: None. The following columnar objects can be modified when the row is in the active state: None

This object specifies the IP address type of a PfR BR.

This object specifies the IP address of a PfR BR

This object specifies the key used to authenticate communication between the BR and the MC. The authentication key must be specified during the initial configuration to establish communication, but is not required to enter PfR managed BR configuration mode.

This object indicates the operational status of PfR BR. 'active' BR is active. 'inactive' BR is inactive. Enumeration: 'active': 1, 'inactive': 2.

This object indicates the connection status between BR and MC. 'up' BR is successfully connected to the MC. 'down' BR is not connected to the MC. Enumeration: 'down': 2, 'up': 1.

This object indicates the length of time that the connection with the MC has been up.

This object indicates the reason why the connection status between the BR and MC fails. 'versionmismatch' The software version between MC and BR does not match. 'none' No failure reason. 'authFailure' authentication failed. 'socketError' socket was closed with an error. 'timerExpired' connection was closed with keepalive timer expiration. Enumeration: 'none': 2, 'authFailure': 3, 'socketError': 4, 'timerExpired': 5, 'versionMismatch': 1.

This object indicates the number of authentication failures between the MC and the BR.

This table lists the PfR exit instances created by the system. This table has an expansion dependent relationship on the cpfrBRTable, containing zero or more rows for each cpfrBREntry.

An entry in the cpfrExitTable describes the configuration and status of one PfR monitored/controlled exit. A peer SNMP entity may create an exit for PfR BR by setting an instance of cpfrLinkGroupRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create an exit for a PfR BR. In these cases, the system must automatically create a row in the cpfrExitTable. A peer SNMP entity may destroy an exit from a PfR BR by setting the corresponding instance of cpfrExitRowStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy an exit from a PfR BR. In these cases, the system must automatically destroy the corresponding row in the cpfrExitTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrBREntry.

This object indicates an arbitrary integer-value that uniquely identifies a PfR monitored/controlled exit.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): cpfrExitName, cpfrExitType, cpfrDowngradeBgpCommunity, cpfrExitMaxUtilRxType, cpfrExitMURxAbsolute, cpfrExitMURxPercentage , cpfrExitMaxUtilTxType, cpfrExitMUTxAbsolute, cpfrExitMUTxPercentage, cpfrExitCostCalcMethod, cpfrExitCostDiscard, cpfrExitCostDiscardType, cpfrExitCostDiscardAbsolute, cpfrExitCostDiscardPercent, cpfrExitCostEndDayOfMonth, cpfrExitCostEndOffset, cpfrExitCostFixedFeeCost, cpfrExitCostNickName, cpfrExitCostSamplingPeriod, cpfrExitCostRollupPeriod, cpfrExitCostSummerTimeStart, cpfrExitCostSummerTimeOffset, cpfrExitCostSummerTimeEnd.

This object specifies the status of a row in the exit table. The following columnar objects must be valid in order to transition the row to the active state: cpfrExitName, cpfrExitType. The following columnar objects can be modified when the row is in the active state: None

This object specifies the name of a PfR controlled interface on a BR.

This object specifies the exit type. 'internal' The interface is an internal interface. Internal interfaces are used for communication between BRs. 'external' The interface is an external interface. External interfaces are used for active and passive monitoring and traffic forwarding. Enumeration: 'internal': 1, 'external': 2.

This object specifies a BGP prepend community number attached to an inside prefix BGP advertisement from the network to another autonomous system. The BGP prepend community will increase the number of autonomous system hops in the advertisement of the inside prefix to other autonomous systems.

This object specifies the maximum utilization configuration type for incoming traffic over a single PfR exit.

This object specifies the maximum utilization on a PfR managed entrance link to an absolute value.

This object specifies the maximum utilization on a PfR managed entrance link to a bandwidth percentage.

This object specifies the maximum utilization configuration type for traffic over a single PfR managed exit.

This object indicates the maximum utilization on a PfR managed exit link to an absolute value.

This object specifies the maximum utilization on a PfR managed exit link to a bandwidth percentage.

This object indicates how the fee for a particular exit is calculated. 'combined' Specifies billing based on combined egress and ingress rollup samples. 'separate' Specifies billing based on separate egress and ingress rollup samples. 'sum' Specifies billing based on egress and ingress rollup samples that are added and then combined. Enumeration: 'sum': 3, 'combined': 1, 'separate': 2.

This object specifies how often rollup samples are discarded. 'daily' Rollup samples are discarded every day. 'monthly' Rollup samples are discarded every month. Enumeration: 'monthly': 2, 'daily': 1.

This object specifies the threshold value types for cost discard. 'absolute' Absolute value configured in cpfrExitCostDiscardAbsolute object will be used. 'percent' Percent value configured in cpfrExitCostDiscardPercent object will be used. Enumeration: 'percent': 2, 'absolute': 1.

This object specifies an absolute number of rollup samples to be discarded.

This object specifies what percentage of the rollup samples should be discarded when calculating the exit cost.

This object specifies the end billing date.

This object indicates the cpfrExitCostEndOffset is before or after cpfrExitCostEndDayOfMonth. 'positive' time After cpfrExitCostEndDayOfMonth. 'negative' time before cpfrExitCostEndDayOfMonth. Enumeration: 'positive': 1, 'negative': 2.

This object indicates an offset in hours and minutes, allowing you to compensate for time zone differences.

This object specifies a non-usage based fixed fee.

This object specifies a nickname for the cost structure.

This object specifies the sampling period.

This object specifies that samples are rolled up at the interval specified for the minutes argument. This value must be greater than or equal to the corresponding instance of cpfrExitCostSamplingPeriod.

This object indicates the date and time when the daylight savings time starts.

This object specifies the offset added in the spring and subtracted in the fall.

This object indicates the date and time when daylight saving time comes to an end.

This object indicates the capacity of the interface.

This object indicates the receive bandwidth as configured on the interface.

This object indicates the transmit bandwidth as configured on the interface.

This object indicates the transmit load of the exit.

This object indicates the receive traffic load of the exit.

The object indicates the exit nickname assigned to an external PfR interface.

This object indicates the exit link cost for the current month.

This object indicates the sustained utilization of the exit link in the current month.

This object indicates the exit link cost of the previous month.

This object indicates the sustained utilization of the exit link for the month prior to the previous month.

This object indicates the exit link cost for the month prior to the previous month.

This object indicates the sustained utilization of the exit link the month prior to the previous month.

This object indicates the total rollups.

This object indicates the total discarded rollups.

This object indicates the left over rollups.

This object indicates the rollups that are being collected.

This object indicates the momentary utilization of the targets.

This object indicates the target when the rollup starts.

This object indicates current rollup target.

This object indicates the cumulative receive bytes in a rollup.

This object indicates the cumulative transmit bytes in a rollup.

This object indicates the remaining time before a new rollup is started.

This object indicates the current status of an exit. 'up' The exit is up. 'down' The exit is down. Enumeration: 'down': 2, 'up': 1.

This object indicates the bandwidth pool for RSVP in PfR.

This table lists the cost tier instances created by the system. This table has an expansion dependent relationship on the cpfrExitTable, containing zero or more rows for each cpfrExitEntry.

An entry describing the configuration of a cost tier of a PfR monitored or Controlled exit. A peer SNMP entity may create a cost tier for a PfR monitored or controlled exit by setting an instance of cpfrExitCostTierRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a cost tier for a PfR monitored or controlled external exit. In these cases, the system must automatically create a row in the cpfrExitCostTierTable. A peer SNMP entity may destroy a cost tier from a PfR monitored or controlled external exit by setting the corresponding instance of cpfrLinkGroupRowStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a cost tier from a PfR monitored or controlled external exit. In these cases, the system must automatically destroy the corresponding row in the cpfrExitCostTierTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrExitEntry.

This object indicates an arbitrary integer-value that uniquely identifies the cost tier of a PfR monitored/controlled exit.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): cpfrExitCostTierFee.

This object specifies the status of a row in the exit cost tier table. The following columnar objects must be valid in order to transition the row to the active state: cpfrExitCostTierFee. The following columnar objects can be modified when the row is in the active state: None

This object specifies the cost value of a cost tier.

This table lists the TC instances created by the system.

An entry describing the metrics that identify a PfR monitored or controlled TC. A device supporting PfR creates a row in a cpfrTrafficClassTable when it recognizes the addition of a new TC monitored by PfR. Likewise, such a device destroys a row in the cpfrTrafficClassTable when a TC has been purged from the system.

This object indicates an arbitrary integer-value that uniquely identifies a TC monitored/controlled by PfR.

This object indicates the index of the BR on which PfR is controlling the TC.

This object indicates the index of the exit on which PfR is controlling the TC.

This object indicates the map index of the PfR map defining the policy for the TC.

This object indicates the map policy index of the PfR map defining the policy for the TC.

This object indicates which objects in the traffic class table are valid. If an attribute of a TC is configured, the corresponding bit in this object should be set. 'source' Source address is valid. 'destination' Destination address is valid. 'sourcePort' Source port object in the entry is valid. 'destinationPort' Destination port object in the entry is valid. 'dscp' DSCP object in the entry is valid. 'protocol' Protocol object in the entry is valid. 'nbar' NBAR object in the entry is valid. Bits: 'protocol': 5, 'destination': 1, 'dscp': 4, 'source': 0, 'destinationPort': 3, 'sourcePort': 2, 'nbar': 6.

This object indicates the type of IP address indicated by the corresponding instance of cpfrTCSrcPrefix.

This object indicates the source IP prefix of the corresponding TC.

This object indicates the prefix length of source IP address for the TC.

This object indicates the minimum source port number for a TC.

This object indicates the maximum source port number for a TC

This object indicates the type of IP address indicated by the corresponding instances of cpfrTCDstPrefix.

This object indicates the destination IP prefix of the corresponding TC.

This object indicates the prefix length of destination IP address for the TC.

This object indicates the minimum destination port of a TC.

This object indicates the maximum destination port of a TC

This object indicates the Differentiated Services Code Point (DSCP) value of a TC.

This object indicates the routing protocol by a TC. Enumeration: 'pbr': 5, 'unknown': 7, 'bgp': 4, 'eigrp': 2, 'static': 1, 'cce': 6, 'ribpbr': 3.

This object indicates the application or protocol recognized by NBAR. The value of this object points to an entry in cnpdSupportedProtocolsTable, which describes the recognized protocol, and is defined in CISCO-NBAR-PROTOCOL-DISCOVERY-MIB.

This table lists the TC status instances created by the system. This table has an one-to-one relationship with cpfrTrafficClassTable, containing a row for each entry in cpfrTrafficClassTable.

An entry describing the status of a PfR monitored or controlled TC. A device supporting PfR creates a row in a cpfrTrafficClassStatusTable when it recognizes the addition of a new TC. Likewise, such a device destroys a row in the cpfrTrafficClassStatusTable when a TC has been purged from the system.

This object indicates the current state of a TC. 'default' The state means that the parent IP routes control the exit for this destination prefix. This would be the same behavior as if PfR were not configured or was shutdown. 'choose' The state indicates PfR is choosing the exit for the prefix. 'holddown' The state is seen when a TC is initially controlled by PfR. This holddown concept is applied to prevent churning or erratic behavior of PfR managed routes from being injected and withdrawn from the IP routing table (and subsequently being redistributed by some IGP) or BGP tables. 'inpolicy' This state means that the prefix meets the policy associated with this prefix or application. 'oopolicy' The prefix or application has been identified as failing to meet its respective policy. Enumeration: 'default': 1, 'oopolicy': 5, 'inpolicy': 4, 'choose': 2, 'holddown': 3.

This object indicates whether a TC was learned or configured. 'learned' The TC is learned by PfR. 'configured' The TC is configured via CLI command. Enumeration: 'learned': 1, 'configured': 2.

This object indicates the index of the learn list responsible for PfR learning this TC.

This object indicates the length of time the TC has been controlled on the current exit.

The object indicates the control state of a TC. 'controlled' PfR is controlling this TC. 'uncontrolled' PfR is not controlling this TC. Enumeration: 'controlled': 1, 'uncontrolled': 2.

This object indicates which routing protocol a TC is being controlled by. 'static' TC is controlled by static routing protocol. 'eigrp' TC is controlled by EIGRP. 'ribpbr' TC is controlled by RIB. 'bgp' TC is controlled by BGP 'pbr' TC is controlled by PBR. 'cce' TC is controlled by CCE. 'unknown' TC os controlled by unknown protocols Enumeration: 'pbr': 5, 'unknown': 7, 'bgp': 4, 'eigrp': 2, 'static': 1, 'cce': 6, 'ribpbr': 3.

This object indicates the time remaining before the prefix timer expires.

This object indicates the time when the last out-of-policy event was observed.

This object indicates the last out-of-policy reason. This object indicates the reason that causes an out-of-policy event. 'delayOOPassiveMode' The Delay is out of policy in passive mode. 'lossOOPassiveMode' The loss is out of policy in passive mode. 'unreachableOOPassiveMode' The unreachability rate is out of policy in passive mode. 'delayOOPActiveMode' The Delay is out of policy in active mode. 'lossOOPActiveMode' The loss is out of policy in active mode. 'unreachableOOPActiveMode' The unreachability rate is out of policy in active mode. 'jitterOOPActiveMode' The jitter is out of policy in active mode. 'mosOOPActiveMode' The mos is out of policy in active mode. 'none' no reason. 'rsvpRecomputeExclude' The TC was excluded by recomputing RSVP bandwidth. Enumeration: 'rsvpOOPRecomputeExclude': 10, 'mosOOPActiveMode': 8, 'none': 9, 'lossOOPActiveMode': 5, 'lossOOPPassiveMode': 2, 'jitterOOPActiveMode': 7, 'delayOOPActiveMode': 4, 'unreachableOOPPassiveMode': 3, 'unreachableOOPActiveMode': 6, 'delayOOPPassiveMode': 1.

This object indicates the value of sysUpTime when the last route change occurred for this TC.

This object indicates the reason the last route change occurred.

This table lists the TC's metrics instances created by the system. This table has an one-to-one relationship with cpfrTrafficClassTable, containing a row for each entry in cpfrTrafficClassTable.

An entry describing the metric for a PfR monitored or controlled TC. A device supporting PfR creates a row in a cpfrTrafficClassMetricTable when it recognizes the addition of a new TC. Likewise, such a device destroys a row in the cpfrTrafficClassMetricTable when a TC has been purged from the system.

This object indicates the value of sysUpTime when the metrics were last updated.

This object indicates the age of a metric.

This object indicates if an object in the entry is valid. 'relativeDelay' Relative delay is a valid value. 'relativeJitter' Relative jitter is a valid value. 'relativeDelayLoss' Relative loss is a valid value. 'relativeDelayUnreachable' Relative unreachability rate is a valid value. 'activeDelay' Absolute delay is a valid value. 'activeJitter' Absolute jitter is a valid value. 'activeLoss' Absolute loss is a valid value. 'activeUnreachable' Absolute unreachable rate is a valid value. 'mosPercentage' Most percentage is a valid value. 'attempts' The number of attempts is a valid value. 'packets' Probe packet is a valid value. 'passiveSTUnreachableAvg' Short time unreachability rate in passive mode is a valid value. 'passiveSTDelayAvg' Short time delay in passive mode is a valid value. 'passiveSTLossAvg' Short time loss in passive mode is a valid value. 'activeSTUnreachableAvg' Short time unreachability rate in active mode is a valid value. 'activeSTDelayAvg' Short time delay in active mode is a valid value. 'passiveLTUnreachableAvg' Long time unreachability rate in passive mode is a valid value. 'passiveLTDelayAvg' Long time delay in passive mode is a valid value. 'passiveLTLossAvg' Long time loss in passive mode is a valid value. 'activeLTUnreachableAvg' Long time unreachability rate in active mode is a valid value. 'activeLTDelayAvg' Long time delay in active mode is a valid value. Bits: 'passiveSTLossAvg': 6, 'passiveLTUnreachableAvg': 9, 'activeSTUnreachableAvg': 7, 'packets': 3, 'activeLTUnreachableAvg': 12, 'activeSTJitterAvg': 0, 'activeSTDelayAvg': 8, 'attempts': 2, 'passiveSTUnreachableAvg': 4, 'mosPercentage': 1, 'activeLTDelayAvg': 13, 'passiveSTdelayAvg': 5, 'passiveLTDelayAvg': 10, 'passiveLTLossAvg': 11.

This object indicates average jitter of a TC in active mode.

This object indicates the number of Mean Opinion Score (MOS) packets with a percentage below threshold in active mode.

This object indicates the number of attempts to send an active probe to a target for this TC.

This object indicates the number packets per jitter probe.

This object indicates the number of the average short term unreachable targets in passive mode.

This object indicates the short term delay as measured by Netflow. The short term interval is 5 minutes.

This object indicates the number of short term packets lost in passive mode.

This object indicates the number of short term unreachable packets in active mode.

This object indicates the short term delay in milliseconds in active mode.

This object indicates the number of long term unreachable packets in flows-per-million in passive mode.

This object indicates the long term delay in milliseconds in passive mode.

This object indicates the number of packets lost over the long term in packets-per-million in passive mode.

This object indicates the number of long term unreachable packets in flows-per-million in active mode.

This object indicates the long term delay in milliseconds in active mode.

This table lists the link group instances created by the system. It has an expansion dependent relationship on cpfrExitTable, containing zero or more rows for each cpfrExitEntry.

An entry describing a link group configured for a PfR monitored or controlled external exit. A peer SNMP entity may create a link group for a PfR monitored or controlled exit by setting an instance of cpfrLinkGroupRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a link group for a PfR monitored or controlled external exit. In these cases, the system must automatically create a row in the cpfrLinkGroupExitTable. A peer SNMP entity may destroy a link group from a PfR monitored or controlled external exit by setting the corresponding instance of cpfrLinkGroupRowStatus to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy a link group from a PfR monitored or controlled external exit. In these cases, the system must automatically destroy the corresponding row in the cpfrLinkGroupExitTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrExitEntry.

This object indicates the name of a link-group.

This object indicates a unique arbitrary number identifying a specific instance in a link-group with the identical name.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this entry is permanent(4): cpfrLinkGroupBRIndex, cpfrLinkGroupExitIndex.

This object specifies the status of a NBAR application list. The following columnar objects must be valid in order to transition the row to the active state: None. The following columnar objects can be modified when the row is in the active state: None

This object specifies the PfR BR on which the exit related to this link group is configured.

This object specifies the exit, identified by this index, in combination with cpfrLinkGroupBRIndex, in cpfrExitTable.

This object indicates PfR Link-Group type. 'primaryLinkGroup' primary link-group 'fallbackLinkGroup' fallback link-group 'none' There is no link-group. Enumeration: 'fallbackLinkGroup': 2, 'primaryLinkGroup': 1, 'none': 3.

This table lists the NBAR list instances created by the system. This table has an expansion dependent relationship on cpfrMatchTable and cpfrLearnListTable, containing zero or more rows for each cpfrMatchEntry and cpfrLearnListEntry.

An entry describing a NBAR application configured in PfR. A peer SNMP entity may create an NBAR application entry by setting an instance of cpfrNbarApplListRowStatus to 'createAndWait' or 'createAndGo'. Observe that an implementation that does not support these option must specify these limitations in an agent capability statement. Other management entities (e.g., the local console) may create a NBAR application. In these cases, the system must automatically create a row in the cpfrNbarApplListTable. A peer SNMP entity may destroy a NBAR application by setting the corresponding instance of cpfrNbarApplListRow Status to 'destroy'. Observe that an implementation that does not support this option must specify this limitation in an agent capability statement. Other management entities may destroy an NBAR application. In these cases, the system must automatically destroy the corresponding row in the cpfrNbarApplListTable. The system automatically destroys rows when the system or EMS/NMS destroys the corresponding entry in cpfrMatchEntry and cpfrLearnListEntry.

This object indicates the name of a NBAR application list.

This object indicates a unique arbitrary number identifying a specific protocol in a PfR NBAR Application List.

This object specifies the memory realization of the row. The following columnar objects are allowed to be writable when the storageType of this conceptual row is permanent(4): cpfrNbarApplPdIndex.

This object specifies the status of a NBAR application list. The following columnar objects must be valid in order to transition the row to the active state: None. The following columnar objects can be modified when the row is in the active state: None

This object indicates the application or protocol recognized by NBAR. The value of this object points to an entry in cnpdSupportedProtocolsTable, which describes the recognized protocol and is defined in CISCO-NBAR-PROTOCOL-DISCOVERY-MIB.

This compliance statement specifies the minimal requirements an implementation must meet in order to claim full compliance with the definition of the CISCO-PFR-MIB.

This compliance statement specifies the new minimal requirements an implementation must meet in order to claim full compliance with the definition of the CISCO-PFR-MIB.

This group contains objects describing PfR MCs and policy maps.

This group contains objects describing PfR Border Router and Exits.

This group contains objects describing PfR TCs.

This group contains new objects describing PfR MCs and policy maps.

This group contains objects describing PfR Border Router and Exits.

A collection of PfR MC notifications.