11-27-2017 11:57 AM
When I set the keep alive on XRv router to 255 the max values allowed I am seeing the below error message - Attempt To Establish Second Session. PCEP session creation fails with its Peer (Controller). Is this a known XRv issue?? What is the max allowed value??
pce
peer source ipv4 10.18.132.97
peer ipv4 10.18.130.92
!
keepalive 255
RP/0/0/CPU0:PCEP_R5#show mpls traffic-eng pce peer ipv4 10.18.130.92
Mon Nov 27 19:01:25.154 UTC
PCE Address 10.18.130.92
State Idle
Precedence 255
Learned through:
Static Config
Sending KA every 25 s
Time out peer if no KA received for 255 s
Tolerance: Minimum KA 10 s
KA messages rxed 2588 txed 19368
PCEReq messages rxed 0, txed 0
PCERep messages rxed 0, txed 0
PCEErr messages rxed 1, txed 69
Last error received: Type 1 Value 1
Last error sent: Type 9 Value 0
PCE OPEN messages: rxed 1068, txed 998
PCEP session ID: local 231, remote 44
Average reply time from peer: 0 ms
Minimum reply time from peer: 0 ms
Maximum reply time from peer: 0 ms
0 requests timed out with this peer
RP/0/0/CPU0:PCEP_R5#
RP/0/0/CPU0:PCEP_R5#RP/0/0/CPU0:Nov 27 19:01:11.875 : te_control[1050]: DBG-PCE-KEEPALIVE[10]: te_pce_process_timers:563: te_pce_process_timers: peer (10.18.130.92) sending KA after 25s
RP/0/0/CPU0:Nov 27 19:01:11.875 : te_control[1050]: DBG-PCE-KEEPALIVE[10]: pce_tx_msg:3580: Sending Keepalive to 10.18.130.92.
RP/0/0/CPU0:Nov 27 19:01:11.875 : te_control[1050]: DBG-PCE-KEEPALIVE[10]: pce_transmit:1753: peer 10.18.130.92 (fd 147) msg_type = Keepalive priority 0
RP/0/0/CPU0:Nov 27 19:01:13.205 : te_control[1050]: DBG-PCE-DETAIL[10]: te_pce_walk_peer_dbase:996: Closing Peer: 10.18.132.97 --> 10.18.130.92
RP/0/0/CPU0:Nov 27 19:01:13.205 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_tx_msg:3585: Sending Close to 10.18.130.92.
RP/0/0/CPU0:Nov 27 19:01:13.205 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_transmit:1748: peer 10.18.130.92 (fd 147) msg_type = Close priority 1
RP/0/0/CPU0:Nov 27 19:01:13.325 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_tcp_close:294: Cannot delete static peer 10.18.132.97 --> 10.18.130.92
RP/0/0/CPU0:Nov 27 19:01:13.325 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_lspmgr_start_lsp_timeouts_ex:836: LSPMgr started timer(s) for LSP 9 (PCEP_R5_t8) (delegation 180, cleanup 0)
RP/0/0/CPU0:Nov 27 19:01:13.325 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_lspmgr_start_lsp_timeouts_ex:836: LSPMgr started timer(s) for LSP 10 (PCEP_R5_t9) (delegation 180, cleanup 0)
RP/0/0/CPU0:Nov 27 19:01:25.414 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_process_peer_sockets:496: pce_process_peer_sockets: Condition 1, Peer state = 3, fd = 147
RP/0/0/CPU0:Nov 27 19:01:25.414 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_process_rx_msg:8278: Open msg, hdr size=[28], bytes read=[28]
RP/0/0/CPU0:Nov 27 19:01:25.414 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_enqueue_simple_error_msg_with_srp:8692: Enqueuing a simple error 9-0 (Attempt To Establish Second Session) message to 10.18.130.92, state = 4 send_and_close Y
RP/0/0/CPU0:Nov 27 19:01:25.414 : te_control[1050]: DBG-PCE-DETAIL[10]: pce_enqueue_simple_error_msg_with_srp:8729: size: [12] length: [12]
12-07-2017 01:34 PM
The range should be 0 to 255.
Note, however, that it is also possible to configure the pce tolerance keepalive value.
Example:
RP/0/RP0/CPU0:router(config-mpls-te)# pce tolerance keepalive 10
(Optional) Configures a PCE tolerance keepalive value (which is the minimum acceptable peer proposed keepalive).
Could it be that the peer has this set to 25 seconds?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide