cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
841
Views
20
Helpful
4
Replies

IOS-XR PCE PEER FLAPS / GOES DOWN IMMEDIATELY

Fayyazii
Level 1
Level 1

PE1 (1.0.1.1)---P1---PCE(1.0.1.99) PCE peer flaps alot, show pce ipv4 shows shows  it comes up for a second and goes down. Below logs shows same. BGP peers are up and stable.

1 - Also PCE connection towards other PEs is stable on 1 peer flaps. I searched on internet but couldnot find what troubleshooting steps can be checked if IGP/BGP peers are stable and pce peer flap. Can someone suggest generally from below logs what might b causing issue and what tshoot steps i can check/?

2- Also, if it shows state TCP pending that what can be the reason n tshoot steps (again IGP/BGP peers shows UP)

 


RP/0/0/CPU0:Dec 16 19:36:09.503 : pce_server[1117]: %OS-PCE-5-PEER_STATE_CHANGE : PCEP Peer 1.0.1.1 state changed from Down to Up
RP/0/0/CPU0:Dec 16 19:36:09.633 : pce_server[1117]: %OS-PCE-5-PEER_STATE_CHANGE : PCEP Peer 1.0.1.1 state changed from Up to Down
RP/0/0/CPU0:Dec 16 19:36:10.573 : pce_server[1117]: %OS-PCE-5-PEER_STATE_CHANGE : PCEP Peer 1.0.1.1 state changed from Down to Up
RP/0/0/CPU0:Dec 16 19:36:10.703 : pce_server[1117]: %OS-PCE-5-PEER_STATE_CHANGE : PCEP Peer 1.0.1.1 state changed from Up to Down
RP/0/0/CPU0:Dec 16 19:36:11.643 : pce_server[1117]: %OS-PCE-5-PEER_STATE_CHANGE : PCEP Peer 1.0.1.1 state changed from Down to Up
RP/0/0/CPU0:Dec 16 19:36:11.763 : pce_server[1117]: %OS-PCE-5-PEER_STATE_CHANGE : PCEP Peer 1.0.1.1 state changed from Up to Down

RP/0/0/CPU0:Dec 16 21:04:40.909 : pce_server[1117]: DBG-PCEP:pce_tx_msg:842 Sending Open to 1.0.1.1.
RP/0/0/CPU0:Dec 16 21:04:40.909 : pce_server[1117]: DBG-PCEP:pce_read_msg:1636 Received OPEN message from 1.0.1.1
RP/0/0/CPU0:Dec 16 21:04:40.909 : pce_server[1117]: DBG-PCEP:pce_process_open_msg:2150 Process OPEN message from 1.0.1.1, ka = 30 dead = 120
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_set_peer_state:161 pce_set_peer_state: Peer 1.0.1.1 state changed from Keep Wait to Up
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: %OS-PCE-5-PEER_STATE_CHANGE : PCEP Peer 1.0.1.1 state changed from Down to Up
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_process_keepalive_msg:1939 Peer 1.0.1.1 transitioning to PCE_STATE_PCEP_OPEN state, next sid 1
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_process_keepalive_msg:1944 In case of stateless PCEP, delete all LSPs
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_process_report_msg:4494 PCReport received from 1.0.1.1: length: 152
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_process_report_msg:4539 obj_class = 33 obj_type = 1 obj_len = 20 rem_len = 148
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_parse_srp_obj:2658 pce_parse_srp_obj: R_flag: 0, SRP-ID: 0
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_process_rp_object_tlv:5148 request has an Path-setup-type TLV Path-setup-type value: Segment-routing
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_process_report_msg:4907 SRP object received
RP/0/0/CPU0:Dec 16 21:04:41.989 : pce_server[1117]: DBG-PCEP:pce_process_report_msg:4539 obj_class = 32 obj_type = 1 obj_len = 52 rem_len = 128
RP/0/0/CPU0:Dec 16 21:04:43.189 : pce_server[1117]: DBG-PCEP:pce_tcp_close:734 Closed TCP connection, clean up peer 1.0.1.1 (static peer no)
RP/0/0/CPU0:Dec 16 21:04:43.189 : pce_server[1117]: DBG-PCEP:pce_set_peer_state:161 pce_set_peer_state: Peer 1.0.1.1 state changed from Up to Idle
RP/0/0/CPU0:Dec 16 21:04:43.189 : pce_server[1117]: %OS-PCE-5-PEER_STATE_CHANGE : PCEP Peer 1.0.1.1 state changed from Up to Down
RP/0/0/CPU0:Dec 16 21:04:43.189 : pce_server[1117]: DBG-PCEP:pce_tcp_close:757 Destroying peer 1.0.1.1
RP/0/0/CPU0:Dec 16 21:04:43.189 : pce_server[1117]: DBG-PCEP:pce_delete_all_non_sync_tun:1260 Peer 1.0.1.1 was not found
RP/0/0/CPU0:Dec 16 21:04:44.159 : pce_server[1117]: DBG-PCEP:pce_create_peer_entry:314 Creating peer entry, from 1.0.1.1 --> 1.0.1.99
RP/0/0/CPU0:Dec 16 21:04:44.159 : pce_server[1117]: DBG-PCEP:pce_set_peer_state:161 pce_set_peer_state: Peer 1.0.1.1 state changed from Closed to Idle
RP/0/0/CPU0:Dec 16 21:04:44.159 : pce_server[1117]: DBG-PCEP:pce_create_peer_entry:407 Created peer entry, from 1.0.1.99 --> 1.0.1.1
RP/0/0/CPU0:Dec 16 21:04:44.159 : pce_server[1117]: DBG-PCEP:pce_set_peer_state:161 pce_set_peer_state: Peer 1.0.1.1 state changed from Idle to Keep Wait
RP/0/0/CPU0:Dec 16 21:04:44.159 : pce_server[1117]: DBG-PCEP:tcp_process_passive_open:1328 Incoming TCP session from 1.0.1.1 to 1.0.1.99 is accepted
RP/0/0/CPU0:Dec 16 21:04:45.269 : pce_server[1117]: DBG-PCEP:pce_create_peer_entry:314 Creating peer entry, from 1.0.1.1 --> 1.0.1.99
RP/0/0/CPU0:Dec 16 21:04:45.269 : pce_server[1117]: DBG-PCEP:pce_set_peer_state:161 pce_set_peer_state: Peer 1.0.1.1 state changed from Closed to Idle
RP/0/0/CPU0:Dec 16 21:04:45.269 : pce_server[1117]: DBG-PCEP:pce_create_peer_entry:407 Created peer entry, from 1.0.1.99 --> 1.0.1.1
RP/0/0/CPU0:Dec 16 21:04:45.269 : pce_server[1117]: DBG-PCEP:pce_set_peer_state:161 pce_set_peer_state: Peer 1.0.1.1 state changed from Idle to Keep Wait
RP/0/0/CPU0:Dec 16 21:04:45.269 : pce_server[1117]: DBG-PCEP:tcp_process_passive_open:1328 Incoming TCP session from 1.0.1.1 to 1.0.1.99 is accepted
RP/0/0/CPU0:Dec 16 21:04:45.269 : pce_server[1117]: DBG-PCEP:pcep_open:610 Opening PCEP for peer 1.0.1.1
RP/0/0/CPU0:Dec 16 21:04:45.269 : pce_server[1117]: DBG-PCEP:pce_enqueue_open_msg:1139 Sending OPEN message (version 1, ka 30, deadtime 120, update cap Y, instantiation cap Y, segment routing cap Y)

1 Accepted Solution

Accepted Solutions

Harold Ritter
Cisco Employee
Cisco Employee

Hi @Fayyazii ,

I have seen this in the past and it ended up being  due to incompatibility between the XR version running on the PE and PCE. What version do you run on the PE that is unstable? What version do you run on the PEs that are stable?

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

4 Replies 4

Harold Ritter
Cisco Employee
Cisco Employee

Hi @Fayyazii ,

I have seen this in the past and it ended up being  due to incompatibility between the XR version running on the PE and PCE. What version do you run on the PE that is unstable? What version do you run on the PEs that are stable?

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 Ritter 

Thank you, i am using it on EVEng with below version

PCE xrv-k9-6.3.1

PE xrv9k-6.5.1

All PE both stable and unstable use 6.5.1

 

Fayyazii
Level 1
Level 1

hi @Harold Ritter 

Your response was helpful, i just changed PCE version to the same as PE and everything is stable. Great help to save time, i spent enough time in going through logs and theory material to find whats causing this issue but could not find it

 

You are very welcome @Fayyazii and thanks for using the Cisco community.

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