[c-nsp] ASR9k LC fib programming problem
Šturmankin Miroslav
miroslav.sturmankin at swan.sk
Mon Aug 7 09:33:46 EDT 2017
Hello folks,
To follow up on the issue, I was able to fix the forwarding problem during a maintenance window by restarting the ipv4_rip process as suggested by James.
RP/0/RSP0/CPU0:a9k6#sh cef vrf inet x.x.x.0/24 location 0/1/CPU0
Fri Aug 4 02:13:33.666 CEST
x.x.x.0/24, version 3115832151, internal 0x4000001 (ptr 0x8a147d64) [1], 0x0 (0x0), 0x0 (0x0)
Updated Nov 9 00:24:29.163
Prefix Len 24, traffic index 0, precedence n/a, priority 3
via a.a.a.2, 3 dependencies, recursive [flags 0x0]
path-idx 0 [0x90220fe4 0x0]
next hop a.a.a.2 via a.a.a.2/32
RP/0/RSP0/CPU0:a9k6#process restart ipv4_rib location 0/RSP0/CPU0
Fri Aug 4 02:13:35.896 CEST
RP/0/RSP0/CPU0:Aug 4 02:13:35.994 : sysmgr_control[65854]: %OS-SYSMGR-4-PROC_RESTART_NAME : User [me] (con0_RSP0_CPU0) requested a restart of process ipv4_rib at 0/RSP0/CPU0
RP/0/RSP0/CPU0:a9k6#sh processes ipv4_rib detail location 0/RSP0/CPU0
Fri Aug 4 02:14:52.508 CEST
Job Id: 1121
PID: 374133031
Executable path: /disk0/iosxr-infra-4.3.4/0x100000/bin/ipv4_rib
Instance #: 1
Version ID: 00.00.0000
Respawn: ON
Respawn count: 2
Max. spawns per minute: 12
Last started: Fri Aug 4 02:13:36 2017
Process state: Run (last exit due to SIGTERM)
Package state: Normal
Process group: v4-routing
core: MAINMEM
Max. core: 0
Level: 170
Mandatory: ON
Placement: Placeable
startup_path: /pkg/startup/ipv4_rib.startup
Ready: 0.556s
Available: 0.571s
Running path: /disk0/iosxr-infra-4.3.4/0x100000/bin/ipv4_rib
Package path: /pkg/bin/ipv4_rib
Job-id-link: 1121
group_jid: 0,0,0,0
fail_count: 0
this pcb: 0xe7ffe848
next pcb: 0x601ef3e0
jobid on RP: 0
Standby Status: 2
Send Avail: YES
role_event_clinfo: 5008bc1c
Proc role state: primary
cleanup_event_clinfo: 0x5008bc1c
Process cpu time: 15.035 user, 0.387 kernel, 15.422 total
JID TID CPU Stack pri state TimeInState HR:MM:SS:MSEC NAME
1121 1 0 188K 10 Receive 0:00:02:0828 0:00:05:0267 ipv4_rib
1121 2 1 188K 10 Receive 0:01:16:0039 0:00:00:0000 ipv4_rib
1121 3 0 188K 10 Receive 0:01:16:0003 0:00:00:0000 ipv4_rib
1121 4 0 188K 10 Receive 0:00:52:0288 0:00:00:0022 ipv4_rib
1121 5 0 188K 10 Sigwaitinfo 0:01:15:0698 0:00:00:0000 ipv4_rib
1121 6 0 188K 10 Receive 0:01:00:0557 0:00:02:0828 ipv4_rib
1121 7 0 188K 10 Receive 0:01:15:0686 0:00:00:0000 ipv4_rib
1121 8 0 188K 10 Receive 0:01:15:0685 0:00:00:0000 ipv4_rib
1121 9 0 188K 10 Receive 0:01:15:0685 0:00:00:0000 ipv4_rib
1121 10 0 188K 10 Receive 0:01:15:0684 0:00:00:0000 ipv4_rib
1121 11 0 188K 10 Receive 0:01:15:0683 0:00:00:0000 ipv4_rib
1121 12 0 188K 10 Receive 0:00:30:0514 0:00:00:0000 ipv4_rib
1121 13 1 188K 10 Receive 0:00:02:0996 0:00:05:0460 ipv4_rib
1121 14 0 188K 10 Receive 0:01:00:0721 0:00:00:0000 ipv4_rib
1121 15 0 188K 10 Receive 0:00:03:0104 0:00:01:0612 ipv4_rib
1121 16 0 188K 10 Receive 0:01:01:0014 0:00:00:0002 ipv4_rib
1121 17 0 188K 10 Receive 0:00:02:0889 0:00:00:0224 ipv4_rib
1121 18 0 188K 10 Receive 0:00:48:0738 0:00:00:0001 ipv4_rib
1121 19 0 188K 10 Receive 0:00:10:0688 0:00:00:0001 ipv4_rib
-------------------------------------------------------------------------------
RP/0/RSP0/CPU0:a9k6#sh cef vrf inet x.x.x.0/24 location 0/1/CPU0
Fri Aug 4 02:15:30.831 CEST
x.x.x.0/24, version 479658, internal 0x4000001 (ptr 0x8a147d64) [1], 0x0 (0x0), 0x0 (0x0)
Updated Aug 4 02:14:07.267
Prefix Len 24, traffic index 0, precedence n/a, priority 3
via b.b.b.2, 8 dependencies, recursive, bgp-ext [flags 0x6020]
path-idx 0 [0x8a1443e4 0x0]
next hop b.b.b.2 via b.b.b.2/32
The restart was hitless without service disruption and it took about ~2mins to reprogram FIB with the correct entry (full BGP in VRF mode).
Thank you all and especially James for support and suggestions.
Regards/S pozdravom,
Miro Sturmankin
-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Šturmankin Miroslav
Sent: pondelok, 17. júla 2017 10:16
To: James Bensley; cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] ASR9k LC fib programming problem
Thanks James, I will schedule a maintenance window and will restart ipv4_rib process. Will keep you posted if it fixed te issue.
Regards/S pozdravom,
Miro Sturmankin
-----Original Message-----
From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of James Bensley
Sent: Friday, July 14, 2017 7:56 PM
To: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] ASR9k LC fib programming problem
On 14 July 2017 at 14:27, Šturmankin Miroslav <miroslav.sturmankin at swan.sk> wrote:
> I did not try any of the disruptive method, yet, as clearing the CEF or restarting RIB as this is a core box doing 40G+ traffic. But if I don't find a way to clear the single CEF entry from LC, I will have to schedule a window. Was the "process restart ipv4_rib" really without a dropped packet? Thanks.
Hi Miro,
We had no problems but were told it "might" cause an issue so best to run those commands during a maintenance window.
Cheers,
James.
_______________________________________________
cisco-nsp mailing list cisco-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list