Ethernet Switching
Ethernet Switching

errors on ex

[ Edited ]
2 weeks ago

Hi all,

In order to find unusual things on EX switch, I executed the junos cli of "clear interfaces statistics all" last Friday. Since then errors are shown below:

1-) From the following outputs, there are 2 collisions(Collisions: 1743 and Collisions: 48 ) are persistintly increasing. The following KB says that Collision always must be zero. Otherwise, there is a software bug.
https://kb.juniper.net/InfoCenter/index?page=content&id=KB24601. What troubleshooting should I do? More further why there is no other errors on these 2 interface as they have collisions errors?
It is realy weird.

 

2-) There is also number of "Carrier transitions:" from output below. One of them is very high and constantly increasing. what troubleshooting must be done for identifying issue.

4500>show interfaces extensive | match "Carrier transitions: [^0]| Errors: [^0]| Drops: [^0]|Collisions: [^0]|CRC errors: [^0]| MTU errors: [^0]"
Carrier transitions: 36, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 48, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 1743, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 4, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 68, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 8, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 65, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 5, Errors: 0, Drops: 0, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 3098, Errors: 0, Drops: 4, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Carrier transitions: 0, Errors: 0, Drops: 4, MTU errors: 0, Resource errors: 0

 

3-) Is there additional pipe that can be add into cli of "show interfaces extensive | match "Carrier transitions: [^0]| Errors: [^0]| Drops: [^0]|Collisions: [^0]|CRC errors: [^0]| MTU errors: [^0]"" to get associated Physical interfaces?

6 REPLIES 6
Ethernet Switching

Re: errors on ex

2 weeks ago

try this one
show interfaces extensive | match "Carrier transitions: [^0]| Errors: [^0]| Drops: [^0]|Collisions: [^0]|CRC errors: [^0]| MTU errors: [^0]| Physical"

Ethernet Switching

Re: errors on ex

2 weeks ago

in most cases Collision errors is due to bad cable / sfp module. Try to replace cable/sfp abd monitor these interfaces

Ethernet Switching

Re: errors on ex

2 weeks ago

Check for Duplex config issue on the peer side. Try to match it manually if auto-negotiation is not giving fruitfull results.

 

-Python JNCIE 3X [SP|DC|ENT] JNCIP-SEC JNCDS 3X [ WAN | DC|SEC] JNCIS-Cloud JNCIS-DevOps CCIP ITIL
#Please mark my solution as accepted if it helped, Kudos are appreciated as well.
Ethernet Switching

Re: errors on ex

2 weeks ago

@ARIX you wrote "The following KB says that Collision always must be zero."  Always is a poor term usage there.  It should say that 'probably should be zero'.  The reason is that most newer Ethernet Devices support Full-Duplex (FDX) operation which eliminates completely any collisions.  'Collision' is an "old time" Ethernet stat, which is still always supported because people still use old devices.  If you are seeing 'collisions' on an interface, it very likely indicates the external attached device is running 10M HDX (half-duplex), or some speed at HDX.

 

In my view, looks like external device is HDX which switch (with auto-neg?) thinks it should be FDX.  This combination is NOT good and although (some) traffic may pass, throughput and performance should be greatly affected.

 

Not sure which exact EX switch model you are using, and what SW version you are on, but if you supply these I might be able to provide further insight, as EX HDX operation may change depending upon the EX model being used.

 

Good luck.

Ethernet Switching

Re: errors on ex

a week ago

Hi Rccpgm,

Thanks reply.. appreciated.

VC consists of 8 ex4200px, version is 5.1R6.7

There 3 interfaces' outputs. First two same conditions, last one is different...Have a look please.

 

Here associated interfaces from being increasing high collisons:

>show interfaces extensive ge-3/0/4

Physical interface: ge-3/0/4, Enabled, Physical link is Up
Interface index: 330, SNMP ifIndex: 893, Generation: 333
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: Auto, Duplex: Auto, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled,
Auto-negotiation: Enabled, Remote fault: Online, Media type: Copper
Device flags : Present Running
Interface flags: Internal: 0x0
Link flags : None
CoS queues : 8 supported, 8 maximum usable queues
Hold-times : Up 0 ms, Down 0 ms
Current address: c0:42:d0:62:b8:07, Hardware address: c0:42:d0:62:b8:07
Last flapped : 2019-08-01 10:17:00 IST (5w5d 02:51 ago)
Statistics last cleared: 2019-09-06 17:46:28 IST (3d 19:22 ago)
Traffic statistics:
Input bytes : 589318962 15336 bps
Output bytes : 755484933 19768 bps
Input packets: 8603212 27 pps
Output packets: 10942171 35 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
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: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 2652, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 6 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 0 10757370 0
1 0 0 0
2 0 0 0
3 0 0 0
5 0 0 0
7 0 184808 0
Queue number: Mapped forwarding classes
0 best-effort
1 bus-app
2 bus-app-interact
3 high-priority
5 expedited-forwarding
7 network-control
Active alarms : None
Active defects : None
MAC statistics: Receive Transmit
Total octets 589318962 755484933
Total packets 8603212 10942171
Unicast packets 8603212 10756230
Broadcast packets 0 1133
Multicast packets 0 184808
CRC/Align errors 0 0
FIFO errors 0 0
MAC control frames 0 0
MAC pause frames 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 2652
Code violations 0
Autonegotiation information:
Negotiation status: Incomplete
Local resolution:
Local link Speed: 10 Mbps, Link mode: Half-duplex
Packet Forwarding Engine configuration:
Destination slot: 3
CoS information:
Direction : Output
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort r r r 0 low none
1 bus-app 25 2500000 25 0 low none
2 bus-app-interact 25 2500000 20 0 low none
3 high-priority 30 3000000 15 0 low none
5 expedited-forwarding r r 5 0 strict-high none
7 network-control 5 500000 5 0 strict-high none
Interface transmit statistics: Disabled

Logical interface ge-3/0/4.0 (Index 255) (SNMP ifIndex 1218) (Generation 320)
Flags: Up SNMP-Traps 0x0 Encapsulation: ENET2
Traffic statistics:
Input bytes : 16380
Output bytes : 22772941
Input packets: 273
Output packets: 185941
Local statistics:
Input bytes : 16380
Output bytes : 22772941
Input packets: 273
Output packets: 185941
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol eth-switch, Generation: 349, Route table: 0
Flags: None

========================================================

>show interfaces extensive ge-3/0/2
Physical interface: ge-3/0/2, Enabled, Physical link is Up
Interface index: 328, SNMP ifIndex: 891, Generation: 331
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: Auto, Duplex: Auto, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled,
Auto-negotiation: Enabled, Remote fault: Online, Media type: Copper
Device flags : Present Running
Interface flags: Internal: 0x0
Link flags : None
CoS queues : 8 supported, 8 maximum usable queues
Hold-times : Up 0 ms, Down 0 ms
Current address: c0:42:d0:62:b8:05, Hardware address: c0:42:d0:62:b8:05
Last flapped : 2019-08-01 20:04:57 IST (5w4d 17:05 ago)
Statistics last cleared: 2019-09-06 17:46:28 IST (3d 19:24 ago)
Traffic statistics:
Input bytes : 589514912 14832 bps
Output bytes : 831000772 20800 bps
Input packets: 8606076 27 pps
Output packets: 12122248 38 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
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: 0
Output errors:
Carrier transitions: 0, Errors: 0, Drops: 0, Collisions: 83, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 6 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 0 11937407 0
1 0 0 0
2 0 0 0
3 0 0 0
5 0 0 0
7 0 184837 0
Queue number: Mapped forwarding classes
0 best-effort
1 bus-app
2 bus-app-interact
3 high-priority
5 expedited-forwarding
7 network-control
Active alarms : None
Active defects : None
MAC statistics: Receive Transmit
Total octets 589514912 831000772
Total packets 8606076 12122248
Unicast packets 8606076 11936279
Broadcast packets 0 1133
Multicast packets 0 184836
CRC/Align errors 0 0
FIFO errors 0 0
MAC control frames 0 0
MAC pause frames 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 83
Code violations 0
Autonegotiation information:
Negotiation status: Incomplete
Local resolution:
Local link Speed: 10 Mbps, Link mode: Half-duplex
Packet Forwarding Engine configuration:
Destination slot: 3
CoS information:
Direction : Output
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort r r r 0 low none
1 bus-app 25 2500000 25 0 low none
2 bus-app-interact 25 2500000 20 0 low none
3 high-priority 30 3000000 15 0 low none
5 expedited-forwarding r r 5 0 strict-high none
7 network-control 5 500000 5 0 strict-high none
Interface transmit statistics: Disabled

Logical interface ge-3/0/2.0 (Index 253) (SNMP ifIndex 1201) (Generation 318)
Flags: Up SNMP-Traps 0x0 Encapsulation: ENET2
Traffic statistics:
Input bytes : 16500
Output bytes : 22730450
Input packets: 275
Output packets: 184837
Local statistics:
Input bytes : 16500
Output bytes : 22730450
Input packets: 275
Output packets: 184837
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol eth-switch, Generation: 347, Route table: 0
Flags: None

============================================================================

What do you think the following interface ?

>show interfaces extensive ge-7/0/37
Physical interface: ge-7/0/37, Enabled, Physical link is Up
Interface index: 459, SNMP ifIndex: 685, Generation: 462
Description: Access device
Link-level type: Ethernet, MTU: 1514, LAN-PHY mode, Speed: Auto, Duplex: Auto, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled, Flow control: Enabled,
Auto-negotiation: Enabled, Remote fault: Online, Media type: Copper
Device flags : Present Running
Interface flags: Internal: 0x0
Link flags : None
CoS queues : 8 supported, 8 maximum usable queues
Hold-times : Up 0 ms, Down 0 ms
Current address: c0:42:d0:63:08:a8, Hardware address: c0:42:d0:63:08:a8
Last flapped : 2019-09-10 13:15:25 IST (00:01:54 ago)
Statistics last cleared: 2019-09-06 17:46:32 IST (3d 19:30 ago)
Traffic statistics:
Input bytes : 239561000 0 bps
Output bytes : 450035696 512 bps
Input packets: 369391 0 pps
Output packets: 818798 1 pps
IPv6 transit statistics:
Input bytes : 0
Output bytes : 0
Input packets: 0
Output packets: 0
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: 0
Output errors:
Carrier transitions: 4260, Errors: 0, Drops: 6, Collisions: 0, Aged packets: 0, FIFO errors: 0, HS link CRC errors: 0, MTU errors: 0, Resource errors: 0
Egress queues: 8 supported, 6 in use
Queue counters: Queued packets Transmitted packets Dropped packets
0 0 625776 0
1 0 0 0
2 0 0 0
3 0 214 0
5 0 0 0
7 0 192807 6
Queue number: Mapped forwarding classes
0 best-effort
1 bus-app
2 bus-app-interact
3 high-priority
5 expedited-forwarding
7 network-control
Active alarms : None
Active defects : None
MAC statistics: Receive Transmit
Total octets 239561000 450035696
Total packets 369391 818798
Unicast packets 347487 468664
Broadcast packets 20 117408
Multicast packets 21884 232726
CRC/Align errors 0 0
FIFO errors 0 0
MAC control frames 0 0
MAC pause frames 0 0
Oversized frames 0
Jabber frames 0
Fragment frames 0
Code violations 0
Autonegotiation information:
Negotiation status: Complete
Link partner:
Link mode: Full-duplex, Flow control: Symmetric/Asymmetric, Remote fault: OK, Link partner Speed: 1000 Mbps
Local resolution:
Flow control: Symmetric, Remote fault: Link OK
Packet Forwarding Engine configuration:
Destination slot: 7
CoS information:
Direction : Output
CoS transmit queue Bandwidth Buffer Priority Limit
% bps % usec
0 best-effort r r r 0 low none
1 bus-app 25 250000000 25 0 low none
2 bus-app-interact 25 250000000 20 0 low none
3 high-priority 30 300000000 15 0 low none
5 expedited-forwarding r r 5 0 strict-high none
7 network-control 5 50000000 5 0 strict-high none
Interface transmit statistics: Disabled

Logical interface ge-7/0/37.0 (Index 364) (SNMP ifIndex 1329) (Generation 429)
Flags: Up SNMP-Traps 0x0 Encapsulation: ENET2
Traffic statistics:
Input bytes : 17802399
Output bytes : 23752149
Input packets: 20018
Output packets: 192884
Local statistics:
Input bytes : 17802399
Output bytes : 23752149
Input packets: 20018
Output packets: 192884
Transit statistics:
Input bytes : 0 0 bps
Output bytes : 0 0 bps
Input packets: 0 0 pps
Output packets: 0 0 pps
Protocol eth-switch, Generation: 458, Route table: 0
Flags: None

Ethernet Switching

Re: errors on ex

a week ago

If the interface is flapping regularly then the carrier transitions count may increase. I see that the other two interfaces have been up for 5w however the interface ge-7/0/37 last flapped 00:01:54 ago and hence the high count of Carrier transition.

 

Thanks