Mailing List Archive: Request for data from PTX PE/Paradise (e.g. PTX1000, LC1101) operators

Hi,

I'd like to return to this topic. I was confused earlier,
misattributing the issue I'm seeing to MX. And now it is clear it must
be on PTX.

I'd again solicit for input for anyone seeing in their syslogs:
a) junos: 'received pdu - length mismatch for lacp'
b) iosxr: 'ROUTING-ISIS-4-ERR_BAD_PDU_LENGTH' or
'ROUTING-ISIS-4-ERR_BAD_PDU_FORMAT'
c) or any other NOS which might log this, when another end is PTX

The issue is very rare, so ideally you'd look at syslog for all
periods you've had Paradise in the network.

Thanks again,
--
++ytti
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

On 6/17/22 11:05, Saku Ytti via juniper-nsp wrote:
> Hi,
>
> I'd like to return to this topic. I was confused earlier,
> misattributing the issue I'm seeing to MX. And now it is clear it must
> be on PTX.
>
> I'd again solicit for input for anyone seeing in their syslogs:
> a) junos: 'received pdu - length mismatch for lacp'
> b) iosxr: 'ROUTING-ISIS-4-ERR_BAD_PDU_LENGTH' or
> 'ROUTING-ISIS-4-ERR_BAD_PDU_FORMAT'
> c) or any other NOS which might log this, when another end is PTX
>
> The issue is very rare, so ideally you'd look at syslog for all
> periods you've had Paradise in the network.

I've checked all our links where a PTX1000 is on end and a CRS-X is on
another, and can't match any such logs.

I'll keep digging.

Mark.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp