Junos and Junosphere
Reply
New User
Tri-Cenential Man
Posts: 1
Registered: ‎11-22-2010
0

L2 Channel Errors Incrementing

Hello Everyone,

 

I've been having issues with L2 Channel Errors incrementing in my routers. I have numerous routers and the speed in which they increment varies. Although there is no production impact of this, it is causing "noise" in the network which interferes with our monitoring. Here are some steps I have tried to isolate the issue:

 

- Disabled CDP on the Cisco switch connected to the Juniper router

- Disabled non-used protocols on our printers (IPX/SPX, Appletalk, etc)

 

Here are the errors, as well as the configurations on both the Juniper and Cisco interfaces:

 

Errors:

Input errors:
    Errors: 0, Drops: 0, Framing errors: 0, Runts: 0, Policed discards: 52804,
    L3 incompletes: 0, L2 channel errors: 77721, L2 mismatch timeouts: 0,
    FIFO errors: 0, Resource errors: 0

 

Interfaces:

Juniper --

vlan-tagging;
speed 100m;
link-mode full-duplex;
gigether-options {
    no-auto-negotiation;
}
unit 0 {
    vlan-id 58;
    family inet {
        address 10.12.58.1/24 {
            preferred;
        }
    }
}
unit 1 {
    vlan-id 63;
    family inet {
        address 10.12.63.1/24 {
            primary;
        }
    }
}

 

Cisco --

interface FastEthernet0/1
 description Uplink to router
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 58,63
 switchport mode trunk
 duplex full
 speed 100
 no cdp enable
end

 

Does anyone have any thoughts on what I can do to isolate these errors? These are remote sites so getting a packet capture would be difficult.

Distinguished Expert
aarseniev
Posts: 1,184
Registered: ‎08-21-2009
0

Re: L2 Channel Errors Incrementing

Hello,

These errors are well documented since very early JUNOS

http://www.juniper.net/techpubs/software/junos/junos40/swcmdref40/html/interfaces-monitor29.html

 

L2 channel errors--The software could not find a valid logical interface (that is, something like ge-1/2/3.0) for an incoming frame. This error increments when, for example, a lookup for a VLAN fails.

 

 

 BAck to Your config example, if a VLAN-tagged Ethernet frame with VLAN-id other than 58 or 63 enters the router interface, it will be dropped and "L2 channel errors" counter incremented.

This could happen if, for instance, your Cisco switch is configured to tag native VLAN (default 1). Control traffic over native VLAN cannot be pruned from Cisco 802.1Q trunks.

Check with "show interface fa0/1 switchport" in CSCO side.

HTH

Regards

Alex

___________________________________
Accept as Solution = cool !
Accept as Solution+Kudo = You are a Star !
Copyright© 1999-2013 Juniper Networks, Inc. All rights reserved.