Thursday, February 8, 2018

Juniper user reporting L2 channel errors on DIA port?

Hello,

So I'm scratching my head on this one as we have a customer (I'm in a provider environment) that is reporting that their hand off port with us is taking scrolling L2 channel errors on their Juniper. We're using a Cisco 6500. I'm not seeing anything wrong on the interface stats on my side either.

Cisco Port Config: Port configuration: interface GigabitEthernet3/10 description Acme Customer ip address X.X.X.X 255.255.255.248 no ip redirects no ip unreachables no ip proxy-arp no cdp enable ip flow ingress end

Juniper Port Config: show interfaces ge-1/0/0 description Acme Provider; unit 0 { family inet { address X.X.X.X/29; } }

[edit]

Their interface stats: show interfaces ge-1/0/0 extensive | grep err Link-level type: Ethernet, MTU: 1514, Link-mode: Full-duplex, 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: 129663, L2 mismatch timeouts: 0, FIFO errors: 0, Resource errors: 0 Output errors: Carrier transitions: 4, 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 Output packet error count 0 Flow error statistics (Packets dropped due to): Incoming NAT errors: 0 User authentication errors: 0 Addresses, Flags: Is-Preferred Is-Primary

Any idea as to what could be causing this? Am I wrong in thinking this is likely purely cosmetic?



No comments:

Post a Comment