3

We are observing resource errors on almost many 1G links on Juniper MX240. The resource errors counter is quite high. The MPC type is MPC Type 1 3D. I am sharing the output of command 'show interface extensive | match Error' as an example.

Can some one clarify what is meant by resource errors and why they occured? How to rectify them?

Junos OS is 15.1R5-S3.4

Many Thanks

//

R1> show interfaces ge-1/0/1 extensive | match Error    
  Link-level type: Flexible-Ethernet, MTU: 1522, MRU: 1530, LAN-PHY mode, Speed: 1000mbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
  Input errors:
    Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0,
    Resource errors: 11485 <-----
  Output errors:
    Carrier transitions: 1, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
    CRC/Align errors                         0                0
    FIFO errors                              0                0
    Total errors                             0                0
    Output packet error count                                 0

R1> show interfaces ge-1/0/3 extensive | match Error    
  Link-level type: Flexible-Ethernet, MTU: 1518, MRU: 1526, LAN-PHY mode, Speed: 1000mbps, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled,
  Input errors:
    Errors: 5, Drops: 0, Framing errors: 5, Runts: 0, Policed discards: 0, L3 incompletes: 0, L2 channel errors: 0, L2 mismatch timeouts: 0, FIFO errors: 0,
    Resource errors: 7433 <-----
  Output errors:
    Carrier transitions: 17, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
    CRC/Align errors                         5                0
    FIFO errors                              0                0
    Total errors                             6                0
    Output packet error count                                 0
1
  • Did any answer help you? If so, you should accept the answer so that the question doesn't keep popping up forever, looking for an answer. Alternatively, you can provide and accept your own answer.
    – Ron Maupin
    Dec 14, 2019 at 20:28

1 Answer 1

3

According to this juniper document it is the sum of transmit drops. This Juniper forum post explains it a bit more:

Basically, when a packet cannot be either put in the buffer or retrieved from the buffer (i.e. when packet is scattered across several buffers due to the pkt size and one of the buffers cannot be accessed) then this counter increments.

I personally have never observed these kinds of errors and have no idea how bad they are or how to get rid of them. I’d open a TAC case for that if I were you.

1
  • Thanks Teun. I personally went through the same Juniper forum page that you mentioned. I just wanted to have more detailed picture of reasons why such errors occurred.
    – Nabeel
    Feb 25, 2019 at 5:51

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.