XR 5.3.1 group regexp syntax

[Mickael Marchand]

Hi,

in XR 4.3.2 I used to have :

group mygroup
 router bgp '.*'
  neighbor '.*'
  !
 !
end-group

to match all neighbors (IPv4 + IPv6)

but I can't make that work with XR 5.3.1 which seems to check the regexp on "neighbor" very hard:

myrtr(config-GRP-bgp)# neighbor '.*'
                                                ^
% Invalid input detected at '^' marker.

the CLI suggests a regexp for IPv4 neighbors, which is accepted :

myrtr(config-GRP-bgp)#neighbor ?
  A.B.C.D or X:X::X  'RegExp': Neighbor address with strict dot/colon match. Eg. '[0-9]*\..*\..*\..*'

router bgp '.*'
  neighbor '[0-9]*\..*\..*\..*'
  !
 !

but it does not propose an IPv6 one and all I tried were rejected ;)

any idea to match IPv6 neighbors ?

thanks

Mik

[xthuijs]

Mik, cant get it to work either, have set this question out to our flex-cli dev team to have a look along.

one of us will report back.

xander

[Mickael Marchand]

same issue with XR 5.3.2 :)

no news from them yet ?

cheers

Mik

[xthuijs · Accepted solution]

Hi Mik,

the parser and flexcli team (thanks Sonia) responded to me that you could try this?

group BGPV6
 router bgp '.*'
  neighbor '::'
   address-family ipv6 unicast
   !
  !
 !
end-group

I haven't given this a twirl myself, so i dunno if that is gonna work :)

xander

[Mickael Marchand]

RP/0/RP0/CPU0:rtr(config)#group BGPV6
RP/0/RP0/CPU0:rtr(config-GRP)# router bgp '.*'
RP/0/RP0/CPU0:rtr(config-GRP-bgp)#  neighbor '::'
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr)#   address-family ipv6 unicast
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr-af)#   !
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr-af)#  !
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr-af)# !
RP/0/RP0/CPU0:rtr(config-GRP-bgp-nbr-af)#end-group
RP/0/RP0/CPU0:rtr(config)#commit
Fri Sep 11 09:14:15.770 UTC
RP/0/RP0/CPU0:Sep 11 09:14:16.154 : config[65900]: %MGBL-CONFIG-6-DB_COMMIT : Configuration committed by user 'xxx'. Use 'show configuration commit changes 1000000314' to view the changes.

that was accepted by the cli at least :)

this really needs to be somewhere in the doc or the cli ;p

thanks Xander

Mik

[xthuijs]

thanks for the confirmation mik, I'll have it documented, besides this forum:)

xander

[Jose Castillo]

Tested the following wildcard with version 5.3.3 and 7.3.3 and with different platforms, both cases it matches the IPv6 peer address.

neighbor '.*:.*::.*'  

[seayu]

'::' doesn't work at all, it doesn't match any IPv6 addresses.

'.*:.*::.*' matches only :: compressed IPv6 address. It doesn't match non-compressed ones like 2001:1:1:1:1:1:1:1. 

'.*:.*::*.+' should match all the IPv6 addresses, and it was accepted by the router config. 

[smilstea]

IPv6 should be something like this:

(([a-f0-9:]+:+)+[a-f0-9]+)



Sam

[seayu]

Hi Sam, 

Yes, your regex string should match all the ipv6 address, but it doesn't accepted by the router. 

RP/0/RSP0/CPU0:router(config)#group test
RP/0/RSP0/CPU0:router(config-GRP)#router bgp '.*'
RP/0/RSP0/CPU0:router(config-GRP-bgp)#neighbor '([a-f0-9:]+:+)+[a-f0-9]+'
^
% Invalid input detected at '^' marker.
RP/0/RSP0/CPU0:router(config-GRP-bgp)#

Thanks, 

Sean