cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
437
Views
0
Helpful
1
Replies

Global parameterization bug in route policies??

evan.r.moore
Level 1
Level 1

On an ASR 9010 running IOS-XR 5.3.3 (freshly turbo-booted):

policy-global
glbLocationCommunity '6',
glbDefaultCustomer '100'
end-global

route-policy test1
set community $glbLocationCommunity additive
end-policy


route-policy test3($p)
set local-preference $p
apply test1
end-policy

This is fine.  Now I enter this:

vt(config)#route-policy test2 ($p)
vt(config-rpl)# set community $glbLocationCommunity additive
vt(config-rpl)# set local-preference $p
vt(config)#commit
Fri Nov 11 17:16:32.420 UTC

% Failed to commit one or more configuration items during a pseudo-atomic operation. All changes made have been reverted. Please issue 'show configuration failed [inheritance]' from this session to view the errors
vt(config)#show conf fail
Fri Nov 11 17:16:48.110 UTC
!! SEMANTIC ERRORS: This configuration was rejected by
!! the system due to semantic errors. The individual
!! errors with each failed configuration command can be
!! found below.


!
route-policy test2($p)
set community $glbLocationCommunity additive
set local-preference $p
end-policy
!
!!% Policy [test2] could not resolve the parameter 'glbLocationCommunity'.
end

vt(config)#abort

Has anyone else seen this?  Is this a bug I didn't know about?  (I know the clock is set in the future; that's not the issue.)

ERM

Bitwrangler for FirstLight Fiber Corp
1 Reply 1

BrianDean
Level 1
Level 1

Found this thread trying to do exactly the same thing. Did you ever find a solution?