21.03.2013 Views

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

Junos® OS Ethernet Interfaces Configuration ... - Juniper Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Description: Test<br />

Flags: SNMP-Traps, Encapsulation: ENET2<br />

Protocol inet, MTU: 1500, Flags: None<br />

Addresses, Flags: Is-Preferred Is-Primary<br />

Destination: 10.115.107.192/29, Local: 10.115.107.193<br />

Broadcast: 10.115.107.199<br />

Meaning The sample output shows where the alarm and other errors might be occurring and any<br />

counters that are incrementing. The only alarm associated with Fast <strong>Ethernet</strong> or Gigabit<br />

<strong>Ethernet</strong> interfaces is the LINK alarm. A LINK alarm indicates a physical problem. To<br />

isolate where the physical problem might be occurring, conduct loopback testing. See<br />

“Checklist for Using Loopback Testing for Fast <strong>Ethernet</strong> and Gigabit <strong>Ethernet</strong> <strong>Interfaces</strong>”<br />

on page 611 for information on conducting a loopback test.<br />

NOTE: Since link status is polled once every second, some items that require<br />

fast link down detection, such as Multiprotocol Label Switching (MPLS) fast<br />

reroute, take longer to execute.<br />

Fast <strong>Ethernet</strong> and Gigabit <strong>Ethernet</strong> Counters<br />

Problem Table 48 on page 623 shows the major counters that appear in the output for the show<br />

interfaces fe-fpc/pic/port extensive and the show interfaces ge-fpc/pic/port extensive<br />

commands. These counters generally increment when there is a problem with a Fast<br />

<strong>Ethernet</strong> or Gigabit <strong>Ethernet</strong> interface. In the Counters column, the counters are listed in<br />

the order in which they are displayed in the output.<br />

Table 48: Major Solution Fast <strong>Ethernet</strong> and Gigabit <strong>Ethernet</strong> Counters<br />

Counter<br />

Input Errors:<br />

Errors<br />

Policed discards<br />

Drops<br />

L3 incompletes<br />

Description<br />

The sum of the incoming frame<br />

aborts and frame check<br />

sequence (FCS) errors.<br />

The frames discarded by the<br />

incoming packet match code.<br />

The number of packets dropped<br />

by the output queue of the I/O<br />

Manager application-specific<br />

integrated circuit (ASIC).<br />

The number of packets<br />

discarded due to the packets<br />

failing Layer 3 header checks.<br />

Copyright © 2012, <strong>Juniper</strong> <strong>Networks</strong>, Inc.<br />

Chapter 35: Investigate Fast <strong>Ethernet</strong> and Gigabit <strong>Ethernet</strong> <strong>Interfaces</strong><br />

Reason for Increment<br />

The frames were discarded because they were not recognized or of<br />

interest. Usually, this field reports protocols that the Junos <strong>OS</strong> does not<br />

handle.<br />

If the interface is saturated, this number increments once for every packet<br />

that is dropped by the ASIC’s random early detection (RED) mechanism.<br />

This counter increments when the incoming packet fails Layer 3 (usually<br />

IPv4) checks of the header. For example, a frame with less than 20 bytes<br />

of available IP header would be discarded and this counter would<br />

increment.<br />

623

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!