cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1504
Views
15
Helpful
24
Replies
Mohideen Pitchai
Beginner

SR TE Policy in IOS XE

Hi , I am trying to bring up SR TE Policy on VIRL to create a tunnel between PEs.

Need support to clarify the following. Kindly assist.

 

1. My PCC to PCE connection doesnt show "Instantiation". Is there anything i am missing here as this is required for SR-PCE initiate LSP if i am not wrong.

 

R5#show pce client peer
PCC's peer database:
--------------------

Peer address: 12.12.12.12, Precedence: 100
Client POLICY_MGR
State up
Capabilities: Stateful, Update, Segment-Routing

 

2. My Policy is not coming up which is created locally on the PCC R5.

 


segment-routing mpls
!
connected-prefix-sid-map
address-family ipv4
5.5.5.5/32 index 5 range 1
exit-address-family
!
segment-routing traffic-eng
policy SR_TE_1
color 10 end-point 3.3.3.3
candidate-paths
preference 100
dynamic
metric
type igp
!

 

Output shows as follows:

 


R5#sh segment-routing traffic-eng policy all

Name: SR_TE_1 (Color: 10 End-point: 3.3.3.3)
Owners : CLI
Status:
Admin: up, Operational: down for 00:43:04 (since 06-21 09:20:51.275)
Candidate-paths:
Preference 100 (CLI):
Dynamic (inactive)
Inactive Reason: Source address is not specified
Metric Type: IGP
Attributes:

 

Note : I am running IOS XE 17.3.1a on VIRL 

 

Thanks
Mohideen.

 

24 REPLIES 24

Hi Harold,

 

Thanks once again.. Below is FYKI. I am running on CML2

 

Please find the available file name from CML as "xrv9k-fullk9-x-7.2.1.qcow2"

 


RP/0/RP0/CPU0:PCE#show install committed
Thu Jun 24 18:03:23.926 UTC
Node 0/RP0/CPU0 [RP]
Boot Partition: xr_lv0
Committed Packages: 12
xrv9k-xr-7.2.1 version=7.2.1 [Boot image]
xrv9k-isis-2.1.0.0-r721
xrv9k-li-x-1.1.0.0-r721
xrv9k-m2m-2.0.0.0-r721
xrv9k-eigrp-1.0.0.0-r721
xrv9k-mgbl-3.0.0.0-r721
xrv9k-mcast-2.1.0.0-r721
xrv9k-ospf-2.0.0.0-r721
xrv9k-mpls-te-rsvp-3.1.0.0-r721
xrv9k-mpls-2.1.0.0-r721
xrv9k-bng-1.0.0.0-r721
xrv9k-k9sec-3.1.0.0-r721

Node 0/0/CPU0 [LC]
Boot Partition: xr_lcp_lv0
Committed Packages: 12
xrv9k-xr-7.2.1 version=7.2.1 [Boot image]
xrv9k-isis-2.1.0.0-r721
xrv9k-li-x-1.1.0.0-r721
xrv9k-m2m-2.0.0.0-r721
xrv9k-eigrp-1.0.0.0-r721
xrv9k-mgbl-3.0.0.0-r721
xrv9k-mcast-2.1.0.0-r721
xrv9k-ospf-2.0.0.0-r721
xrv9k-mpls-te-rsvp-3.1.0.0-r721
xrv9k-mpls-2.1.0.0-r721
xrv9k-bng-1.0.0.0-r721
xrv9k-k9sec-3.1.0.0-r721

Hi Mohideen,

 

It looks good. The issue is somewhere else. Can you please share the PCE configuration.

 

Regards,

 

 

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Hi Harold,

 

Attached configuration is FYKI.

 

Thank you

Hi @Harold Ritter  I am sharing you the "pce_server" process status looks all sleeping.

 

Hi Mohideen,

 

The issue is due to the fact that you are missing the following configuration under the ospf process on the PCE.

 

router ospf SR

 distribute link-state

 

This is why the PCE is not listening on TCP port 4189

 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

View solution in original post

Hi Harold,

 

Its working now. Thanks for your support to reach towards conclusion.. Much appreciated.

 

Thanks

Mohideen.

View solution in original post

Hi @Mohideen Pitchai ,

 

It looks like you might be missing some configuration between the source and destination.

 

Can you run the following command to verify that:

 

sh segment-routing traffic-eng cspf ipv4 source <lo0 source for the LSP> destination 1.1.1.1 metric-type igp

 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Hi Harold,

 

Please find below output. i have attached my running configuration along with some more output for your kind reference.

 


R5#show segment-routing traffic-eng cspf ipv4 source 5.5.5.5 destination 1.1.1.1 metric-type igp
No Path Found

CSPF result: Not set (rc=0)

 

Thanks

Mohideen

The issue seems to be due to the fact that your OSPF network type is not point-to-point.

 

This causes weird information in the segment routing topology database as can be seen here:

 

Node 1:
TE router ID: 5.5.5.5
OSPF router ID: 5.5.5.5 area ID: 0 domain ID: 115 ASN: 0
Prefix SID:
Prefix 5.5.5.5, label 16005 (regular), domain ID 115, flags: N
Link[0]: local address 10.1.5.5, remote address 10.1.5.1
Local node:
OSPF router ID: 5.5.5.5 area ID: 0 domain ID: 115 ASN: 0
Remote node:
TE router ID: 1.1.1.1
OSPF router ID: 1.1.1.1 area ID: 0 domain ID: 115 ASN: 0
Metric: IGP 0, TE 0, Delay 0
Bandwidth: Total 0, Reservable 0
Admin-groups: 0x00000000
Link[1]: local address 10.1.5.5, remote address 10.1.5.5
Local node:
OSPF router ID: 5.5.5.5 area ID: 0 domain ID: 115 ASN: 0
Remote node:
TE router ID: 5.5.5.5
OSPF router ID: 5.5.5.5 area ID: 0 domain ID: 115 ASN: 0
Metric: IGP 1, TE 1, Delay 1
Bandwidth: Total 125000000, Reservable 0
Admin-groups: 0x00000000
Adj SID: 18 (unprotected)

 

Although you only have one link between Node 1 and Node 2, the topology database sees 2. 

 

Can you please set all the transit interface as point-to-point ("ip ospf network point-to-point").

 

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

View solution in original post

 Hi Harold,

 

Thats great.. After modifying P2P , the policy came up. Thanks a lot. I am still looking forward your support to overcome on PCEP issue which is keep flapping.

 


R5#sh segment-routing traffic-eng policy all

Name: SR_TE (Color: 5 End-point: 1.1.1.1)
Owners : CLI
Status:
Admin: up, Operational: up for 01:00:38 (since 06-23 06:28:41.119)
Candidate-paths:
Preference 5 (CLI):
Dynamic (active)
Metric Type: IGP, Path Accumulated Metric: 1
18 [Adjacency-SID, 10.1.5.5 - 10.1.5.1]
Attributes:
Binding SID: 17
Allocation mode: dynamic
State: Programmed

 

PCEP is keep flapping.

 

R5#show pce client peer
PCC's peer database:
--------------------

Peer address: 12.12.12.12, Precedence: 10
Client POLICY_MGR
State keep wait
Capabilities: Stateful, Update, Segment-Routing

R5#show pce client peer
PCC's peer database:
--------------------

Peer address: 12.12.12.12, Precedence: 10
Client POLICY_MGR
State idle
Capabilities: Stateful, Update, Segment-Routing

R5#show pce client peer
PCC's peer database:
--------------------

Peer address: 12.12.12.12, Precedence: 10
Client POLICY_MGR
State up
Capabilities: Stateful, Update, Segment-Routing

 

Thanks

Mohideen.