cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
677
Views
0
Helpful
4
Replies

Loopback for pce peer source

coolexer1987
Level 1
Level 1

Hello!

Software IOS-XR 6.0.1

Can I use loopback address for comand Loopback for "mpls traffic-eng pce peer source ipv4" ?

When I set the ip address from loopback the packets stop to send.

It's a strange behavior to use only physical interface because:

1) Loopback provides redundancy

2) subnets for physical ptp interfaces are not available for management very often. 

Thanks in advance

1 Accepted Solution

Accepted Solutions

here is a config snippet that our dev test used for verification:

pce

  peer source ipv4 192.168.168.168

  deadtimer 120

  peer ipv4 192.168.1.1

  !

  peer ipv4 192.168.178.178

  !

  logging events peer-status

  keepalive 60

  stateful-client

   instantiation

   report

   fast-repair

  !

  reoptimize 240

  tolerance keepalive 25

ipv4 unnumbered mpls traffic-eng Loopback0

interface Loopback0

ipv4 address 192.168.168.168 255.255.255.2

maybe the bold line is missing in yours?

xander

View solution in original post

4 Replies 4

xthuijs
Cisco Employee
Cisco Employee

hi coolexer,

technically this should work, it makes sense for it to be a loopback addr as you mention.

the addr is used as a source for the tcp connections hence makes sense to be redundantly available.

there may be a stipulation with lpts (hole piercing) but it sounds like that no packet is sent at all when that source is selected?

even if not supported, documentation should reflect taht restriction which is not there either.

would recommend to file a tac case with the show tech mpls traffic-eng to have this evaluated and corrected either with documentation or sw.

cheers

xander

Hello xthuijs!

Yes, technically it should work because it usual function.

But when I change ip address from physical interface to loopback It doesn't send pcep packets at all...

Of cource I can ping loopback from PCE server.

 

here is a config snippet that our dev test used for verification:

pce

  peer source ipv4 192.168.168.168

  deadtimer 120

  peer ipv4 192.168.1.1

  !

  peer ipv4 192.168.178.178

  !

  logging events peer-status

  keepalive 60

  stateful-client

   instantiation

   report

   fast-repair

  !

  reoptimize 240

  tolerance keepalive 25

ipv4 unnumbered mpls traffic-eng Loopback0

interface Loopback0

ipv4 address 192.168.168.168 255.255.255.2

maybe the bold line is missing in yours?

xander

I checked with the TE dev team and indeed this is supported and should work.

we need to investigate this more why it doesnt.

it might be best to look at XR602 or 61<latest> however instead of 601.

the tech mpls te would help as well as some debugs to see how it gets initiated and if the packets are generated properly.

xander