Re: OER master active-probe

thanks guys. feeling more comfertable with this config.

On Sun, Apr 22, 2012 at 4:23 PM, Ben Hughes <bhughes_at_imc.net.au> wrote:
>
> Hi Marc,
>
> The policy-rules command tells the oer master process to use the oer-map specified elsewhere. Whether active probing is being used or not depends on your monitor mode which can be set in the oer-map. If it's not set in the oer-map I think it would fall back to whatever is set in global policy.
>
> So from the initial config you posted there should be a section starting with "oer-map prfx" that is separate to the "oer master" section.
>
> cheers,
> Ben.
>
>
>
> From: marc edwards <renorider_at_gmail.com<mailto:renorider_at_gmail.com>>
> Reply-To: marc edwards <renorider_at_gmail.com<mailto:renorider_at_gmail.com>>
> Date: Monday, 23 April 2012 8:00 AM
> To: Vijaya Laxmi <vj.laxmi86_at_gmail.com<mailto:vj.laxmi86_at_gmail.com>>
> Cc: Adrian Mornaila <adiem77_at_gmail.com<mailto:adiem77_at_gmail.com>>, Cisco certification <ccielab_at_groupstudy.com<mailto:ccielab_at_groupstudy.com>>
> Subject: Re: OER master active-probe
>
> Thanks that was the issue. I guess my other question for more clarity
> in the configuration...
>
> what exactly is
> policy-rules prfx
>
> doing and is this linked to the oer-map active probing?
>
> Thanks,
>
> Marc
>
>
> On Sun, Apr 22, 2012 at 2:38 PM, Vijaya Laxmi <vj.laxmi86_at_gmail.com<mailto:vj.laxmi86_at_gmail.com>> wrote:
> From what I hdvh seen....
>
> I would say it is a Must to put set mode monitor active under oer-map for
> particular prefix
>
> Vijaya
>
> Sent from my %brant0
>
> On Apr 22, 2012 4:34 PM, "marc edwards" <renorider_at_gmail.com<mailto:renorider_at_gmail.com>> wrote:
>
> Problem was I didn't have an oer-map that matched the prefix. Any
> active probe will need oer map....? please confirm or correct this
> statement.
>
> R6#sh run | b ^oer-map
> oer-map prfx 10
> match traffic-class prefix-list prfx
>
> R6#sh oer master active-probes
> OER Master Controller active-probes
> Border = Border Router running this Probe
> State = Un/Assigned to a Prefix
> Prefix = Probe is assigned to this Prefix
> Type = Probe Type
> Target = Target Address
> TPort = Target Port
> How = Was the probe Learned or Configured
> N - Not applicable
>
> The following Probes exist:
>
> State Prefix Type Target TPort How
> Codec
> Assigned 3.3.3.3/32 echo 3.3.3.3 N Cfgd
> N
>
> The following Probes are running:
>
> Border State Prefix Type Target TPort
> 1.1.1.6 ACTIVE 3.3.3.3/32 echo 3.3.3.3 N
>
>
> Thanks,
> Marc
>
> On Sun, Apr 22, 2012 at 1:16 PM, marc edwards <renorider_at_gmail.com<mailto:renorider_at_gmail.com>> wrote:
>> Experts,
>>
>> I am running through a lab on OER. When I look at the sh oer master
>> active-probe output on my rack I see:
>> ----
>> R6#sh oer master active-probes
>> OER Master Controller active-probes
>> Border = Border Router running this Probe
>> State = Un/Assigned to a Prefix
>> Prefix = Probe is assigned to this Prefix
>> Type = Probe Type
>> Target = Target Address
>> TPort = Target Port
>> How = Was the probe Learned or Configured
>> N - Not applicable
>>
>> The following Probes exist:
>>
>> State Prefix Type Target TPort How
>> Codec
>> Unassigned echo 3.3.3.3 N Cfgd
>> N
>>
>> The following Probes are running:
>>
>> Border State Prefix Type Target
>> TPort
>> ----
>> When I look at answer key it shows:
>> ---
>> OER Master Controller active-probes
>> Border = Border Router running this Probe
>> = Probe is assigned to this Prefix
>> State = Un/Assigned to a Prefix
>> Prefix
>>
>> Type = Probe Type
>> Target = Target Address
>> TPort = Target Port
>> llowing Probes exist:
>> tate Prefix
>>
>> S
>> How = Was the probe Learned or Configured
>> N - Not applicable
>>
>> The
>> f
>> o Type Target TPort How
>> Assigned 3.3.3.3/32 echo 3.3.3.3 N Cfgd
>> The following Probes are running:
>>
>> Border State Prefix Type Target TPo
>> r1.1.1.6 ACTIVE 3.3.3.3/32 echo 3.3.3.3
>> N
>> ----
>>
>> Any ideas why my state is unassigned? Here is configuration from router
>>
>>
>> R6#sh run | b ^oer
>>
>> oer master
>> policy-rules prfx
>> logging
>> !
>> border 1.1.1.6 key-chain OER
>> interface Serial0/0/0.62 external
>> interface FastEthernet0/1 external
>> interface FastEthernet0/0 internal
>> !
>> learn
>> delay
>> periodic-interval 3
>> monitor-period 1
>> no max range receive
>> mode route control
>> mode monitor active
>> !
>> active-probe echo 3.3.3.3
>> !
>> oer border
>> logging
>> local FastEthernet0/0
>> master 1.1.1.6 key-chain OER
>> !
>> ip prefix-list prfx seq 5 permit 3.3.3.3/32
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Sun Apr 22 2012 - 18:07:29 ART