cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
1551
Views
0
Helpful
1
Replies
Highlighted
Frequent Contributor

oer/pfr uncontrol prefix

Hi guys,

I am studying oer/pfr feature and I followed the scenario presented here.

As all things seem to work well, I got stuck at the middle of the scenario. I generate some traffic pinging from R1 to the direction of R11. Traffic flows well and OER learning phase goes well, untill I receive these messages:

*Mar  2 01:50:08.541: %OER_MC-5-NOTICE: Prefix Learning WRITING DATA

*Mar  2 01:50:08.565: %OER_MC-5-NOTICE: Prefix Learning STARTED

R3(config-oer-mc)#

*Mar  2 01:50:59.681: %OER_MC-5-NOTICE: Uncontrol Prefix 20.10.11.0/24, Couldn't find the best exit

*Mar  2 01:50:59.685: %OER_MC-5-NOTICE: Uncontrol Prefix 20.10.11.0/24, Couldn't choose exit in prefix timeout

R3(config-oer-mc)#

*Mar  2 01:51:09.461: %OER_MC-5-NOTICE: Prefix Learning WRITING DATA

*Mar  2 01:51:09.477: %OER_MC-5-NOTICE: Prefix Learning STARTED

R3(config-oer-mc)#

*Mar  2 01:51:19.261: %OER_MC-5-NOTICE: Discovered Exit for Prefix 20.10.11.0/24, BR 10.5.5.5, i/f Fa0/1

And when issuing show oer master traff

DstPrefix           Appl_ID Dscp Prot     SrcPort     DstPort SrcPrefix        

           Flags             State     Time            CurrBR  CurrI/F Protocol

         PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos      EBw      IBw

         ActSDly  ActLDly   ActSUn   ActLUn  ActSJit  ActPMOS

--------------------------------------------------------------------------------

20.10.11.0/24             N defa    N           N           N N                

                          DEFAULT*      656          10.5.5.5    Fa0/1        U

               U        U        0        0        0        0        0        0

               U        U        0  1000000        N        N

it keep showing 20.10.11.0/24 in the DEFAULT state. Search told me:

PfR Traffic Class States

The table below summarizes the possible TC states:

DEFAULTA network prefix may be shown in the default state if it is manually configured or learned, but has not been determined to be in or out-of-policy. Prefixes may revert back to default state if, for some reason, OER can no longer control the prefix. This may happen if all the exits are out-of-policy. The default state means that the parent IP routes control the exit for this destination prefix. This would be the same behavior as if OER were not configured or shutdown.

Now, if anyone can guide me how to solve this "uncontrol prefixes" state and move on to finally see pfr doing its job.

Here is the MC configuration:

oer master

max-range-utilization percent 10

logging

!

border 10.4.4.4 key-chain prf

  interface FastEthernet0/1 external

   max-xmit-utilization percentage 90

  interface FastEthernet0/0 internal

!

border 10.5.5.5 key-chain prf

  interface FastEthernet0/1 external

   max-xmit-utilization percentage 90

  interface FastEthernet0/0 internal

!

learn

  throughput

  delay

  periodic-interval 0

  monitor-period 1

no max range receive

unreachable relative 10

loss relative 5

holddown 90

mode route control

periodic 180

resolve range priority 1

resolve utilization priority 5 variance 20

no resolve delay

!

Also show oer master:

OER state: ENABLED and ACTIVE

  Conn Status: SUCCESS, PORT: 3949

  Version: 2.1

  Number of Border routers: 2

  Number of Exits: 2

  Number of monitored prefixes: 1 (max 5000)

  Max prefixes: total 5000 learn 2500

  Prefix count: total 1, learn 1, cfg 0

Border           Status   UP/DOWN             AuthFail  Version

10.5.5.5         ACTIVE   UP       1d01h          0  2.1

10.4.4.4         ACTIVE   UP       1d01h          0  2.1

Global Settings:

  max-range-utilization percent 10 recv 0

  mode route metric bgp local-pref 5000

  mode route metric static tag 5000

  trace probe delay 1000

  logging

Default Policy Settings:

  backoff 300 3000 300

  delay relative 50

  holddown 90

  periodic 180

  probe frequency 56

  mode route control

  mode monitor both

  mode select-exit good

  loss relative 5

  jitter threshold 20

  mos threshold 3.60 percent 30

  unreachable relative 10

  resolve range priority 1 variance 0

  resolve utilization priority 5 variance 20

Learn Settings:

  current state : STARTED

  time remaining in current state : 88 seconds

  throughput

  delay

  no inside bgp

  no protocol

  monitor-period 1

  periodic-interval 0

  aggregation-type prefix-length 24

  prefixes 100

  expire after time 720


Everyone's tags (4)
1 REPLY 1
Frequent Contributor

Re: oer/pfr uncontrol prefix

Hello again,

One month later and I retry to catch up with OER/pFR.

This time I setup on REAL equipments (previous scenario was run in GNS3). Here is the root scenario I started on; unfortunately I am stuck at the beginning, as I can't reach an OOP.

Here is the message I receive just after I enable the CRITICALL-TRAFFIC policy:

*Oct  2 00:15:03: %OER_MC-5-NOTICE: Uncontrol Prefix 31.1.1.0/24, Couldn't find the best exit

*Oct  2 00:15:03: %OER_MC-5-NOTICE: Uncontrol Prefix 31.1.1.0/24, Couldn't choose exit in prefix timeout

show oer master traffic-class
*Oct  2 00:19:01: %SYS-5-CONFIG_I: Configured from console by console
Cisco-1812f#show oer master traffic-class
OER Prefix Statistics:
Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
P - Percentage below threshold, Jit - Jitter (ms),
MOS - Mean Opinion Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied

DstPrefix           Appl_ID Dscp Prot     SrcPort     DstPort SrcPrefix        
           Flags             State     Time            CurrBR  CurrI/F Protocol
         PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos      EBw      IBw
         ActSDly  ActLDly   ActSUn   ActLUn  ActSJit  ActPMOS  ActSLos  ActLLos
--------------------------------------------------------------------------------
31.1.1.0/24               N defa    N           N           N N                
                          DEFAULT*      @31          10.5.5.5      Fa0        U

*Oct  2 00:15:03: %OER_MC-5-NOTICE: Uncontrol Prefix 31.1.1.0/24, Couldn't find the best exit
*Oct  2 00:15:03: %OER_MC-5-NOTICE: Uncontrol Prefix 31.1.1.0/24, Couldn't choose exit in prefix timeout

This is how the traffic class looks:

show oer master traffic-class
*Oct  2 00:19:01: %SYS-5-CONFIG_I: Configured from console by console
Cisco-1812f#show oer master traffic-class
OER Prefix Statistics:
Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
P - Percentage below threshold, Jit - Jitter (ms),
MOS - Mean Opinion Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied

DstPrefix           Appl_ID Dscp Prot     SrcPort     DstPort SrcPrefix        
           Flags             State     Time            CurrBR  CurrI/F Protocol
         PasSDly  PasLDly   PasSUn   PasLUn  PasSLos  PasLLos      EBw      IBw
         ActSDly  ActLDly   ActSUn   ActLUn  ActSJit  ActPMOS  ActSLos  ActLLos
--------------------------------------------------------------------------------
31.1.1.0/24               N defa    N           N           N N                
                          DEFAULT*      @31          10.5.5.5      Fa0        U

Any insights on this one?

L.E. I run OER v2.2 both on MC and BRs.

CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards