cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2704
Views
5
Helpful
4
Replies

XR RPL parametrization

blau grana
Level 7
Level 7

Hi All,

I have issues to create RPL with multiple parameters:

RP/0/0/CPU0:PE1(config)#show configuration failed
Sat Jan  7 14:49:44.121 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.

router bgp 64500
 neighbor 192.168.11.2
  address-family ipv4 unicast
   route-policy EBGP_IN(64501, 200, 64500:20) in
!!% Verify failed for policy: Mismatch in number of parameters passed to policy at an attachpoint.
  !
 !
!
end

RP/0/0/CPU0:PE1(config)#do sh run route-policy EBGP_IN
Sat Jan  7 14:49:54.011 UTC
route-policy EBGP_IN($ORIG, $LOC_PREF, $COMM)
  if as-path originates-from '$ORIG'  then
    set local-preference $LOC_PREF
    set community $COMM
  else
    drop
  endif
end-policy

RP/0/0/CPU0:PE1#sh ver
Cisco IOS XR Software, Version 5.3.0[Default]
Copyright (c) 2015 by Cisco Systems, Inc.

Can anyone spot what could be a problem?

thanks

Best Regards Please rate all helpful posts and close solved questions
1 Accepted Solution

Accepted Solutions

Aleksandar Vidakovic
Cisco Employee
Cisco Employee

Use "commit show-error" instead of "commit" and you will see what you need to do to make this work.

hope this helps,

/Aleksandar

View solution in original post

4 Replies 4

Aleksandar Vidakovic
Cisco Employee
Cisco Employee

Use "commit show-error" instead of "commit" and you will see what you need to do to make this work.

hope this helps,

/Aleksandar

Hi Aleksandar,

Very useful command, thank you!

It turned out I had to specify community-set and use it inside route-policy instead of directly writing community.

RP/0/0/CPU0:PE1(config)#commit show-error 
% Failed to commit one or more configuration  items during a pseudo-atomic operation. All changes made have been reverted.
 !! 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.

router bgp 64500
 neighbor 192.168.11.2
  address-family ipv4 unicast
   route-policy EBGP_IN(64501, 200, 64500:20) in
!!% Could not find entry in list: Policy [EBGP_IN] uses community set [64500:20]. [64500:20] must be defined before [EBGP_IN] can be attached.
  !
 !
!
end
.
.
.
RP/0/0/CPU0:PE1(config)#sh conf
community-set COMM-AS64501
  64500:20,
  64500:64501
end-set
!
router bgp 64500
 neighbor 192.168.11.2
  address-family ipv4 unicast
   no route-policy EBGP_IN(64501, 200, 64500:20) in
   route-policy EBGP_IN(64501, 200, COMM-AS64501) in
  !
 !
!
end

RP/0/0/CPU0:PE1(config)#commit
RP/0/0/CPU0:PE1(config)#
Best Regards Please rate all helpful posts and close solved questions

great! I'm happy to see that the issue is resolved. :)

AARON WEINTRAUB
Level 1
Level 1

You can't pass in a "complex" variable with a :.  You can pass in just the right (or left) part of a community in that manner (or pass in both halves separately, A,B) , so pass in '20' and then set community 64501:$COMM, or you can possibly try to pass the community as a 32 bit number (both halves as just one number) but I'm not sure that is supported.  The parameterization in RPL is not as fully intuitive as I would like.