[f-nsp] High CPU on LP

[Eldon Koyle]

Are you learning a more specifc route to your gre peer over the tunel?  If
so, you will probably need some static routes so you don't try to route
your gre tunnel through itself.

-- 
Eldon

On Mar 29, 2017 11:59 PM, "Youssef Bengelloun-Zahr" <bengelly at gmail.com>
wrote:

Also, what code version are you running ?

Best regards.



Le 30 mars 2017 à 07:57, Eldon Koyle <ekoyle+puck.nether.net at gmail.com> a
écrit :

What protocols are you running over the GRE tunnel?

It might be helpful to include the GRE config from both sides.

The diagnostic guide says drop code 55 / Layer 3 invalid FID(PFE) means
"the forwarding information for a layer 3 packet is invalid in software".

-- 
Eldon

On Mar 29, 2017 11:23 PM, "Daniel Zilla" <dzilla833 at yandex.com> wrote:

> Formatting;
>
> Hello List
>
> LP CPU is stuck at 96-100% when receiving traffic over a configured GRE
> tunnel
>
> MLX-4
> NI-MLX-10Gx4
>
> Debug packet capture shows many of these
>
> [ppcr_tx_packet] ACTION: Drop packet(reason: Layer 3 invalid FID(PFE))
> [ppcr_rx_packet]: Packet received
> Time stamp : 188 day(s) 12h 45m 15s:,
> TM Header: [ 8016 1000 0000 ]
> Type: Fabric Unicast(0x00000008) Size: 88 Parity: 1 Src IF: 0
> Src Fap: 0 Dest Port: 0  Src Type: 0 Class: 0x00000000
> **********************************************************************
> Packet size: 82, XPP reason code: 0x00006868
> FID     = 0x0001
>   Offset  = 0x10
>   VLAN    = 100(0x0064)
>   CAM     = 0x135ad(R)
>   SFLOW   = 0
>   DBL TAG = 0
>
> Pri CPU MON SRC   PType US BRD DAV SAV DPV SV ER TXA SAS Tag MVID
> 0   1   0   1/1   0     1  0   0   0   1   0  0  1   1   1   0
>
> The issue only occurs when traffic is sent over the GRE tunnel otherwise
> CPU is 1 - 2 %
>
> Management CPU is low all the time, LP is the only problematic
>
> Show tasks indicates LP-RX-Pak is 96% : main is 2%
>
> No route-only mode is enabled on this chassis.
>
> Cheers
>
>
> 30.03.2017, 01:18, "Daniel Zilla" <dzilla833 at yandex.com>:
>
> Hello List
>
> LP CPU is stuck at 96-100% when receiving traffic over a configured GRE
> tunnel
>
> MLX-4
> NI-MLX-10Gx4
>
> Debug packet capture shows many of these
>
> [ppcr_tx_packet] ACTION: Drop packet(reason: Layer 3 invalid FID(PFE))
> [ppcr_rx_packet]: Packet received
> Time stamp : 188 day(s) 12h 45m 15s:,
> TM Header: [ 8016 1000 0000 ]
> Type: Fabric Unicast(0x00000008) Size: 88 Parity: 1 Src IF: 0
> Src Fap: 0 Dest Port: 0  Src Type: 0 Class: 0x00000000
> **********************************************************************
> Packet size: 82, XPP reason code: 0x00006868
> FID     = 0x0001
>   Offset  = 0x10
>   VLAN    = 100(0x0064)
>   CAM     = 0x135ad(R)
>   SFLOW   = 0
>   DBL TAG = 0
>
> Pri CPU MON SRC   PType US BRD DAV SAV DPV SV ER TXA SAS Tag MVID
> 0   1   0   1/1   0     1  0   0   0   1   0  0  1   1   1   0
>
> The issue only occurs when traffic is sent over the GRE tunnel otherwise
> CPU is 1 - 2 %
>
> Management CPU is low all the time, LP is the only problematic
>
> Show tasks indicates LP-RX-Pak is 96% : main is 2%
>
> No route-only mode is enabled on this chassis.
>
> Cheers
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20170330/c4ec4b48/attachment.html>