'인터페이스'에 해당되는 글 1건

  1. 2009.05.21 cisco장비 인터페이스 정보들

네트웍장비들의 인터페이스의 성능을 모니터링하기 위해 주로 사용하는 용어들을 시스코사중심으로 정리해 보았다. 다른 장비에서 크게 차이는 없다.

 

runt : 이더넷에서 64 byte 이하의 크기를 가진 이더넷 frame을 수신하였을 때 증가

giants: CRC를 포함하여 1518byte 이상의 크기를 가진 frame을 수신하였을 대 증가(preamble 제외)

input errors: no buffer,runts,giants,CRCs,frame,overrun,ignored 를 총합산한 에러 frame수

CRC: 입력 패킷에 대한 CRC에러 발생 수

frame: 8bit 로 된 byte 단위로 끝나지 않은 잘못된 frame을 수신한 수

overrun: input rate가 한계치를 넘어서 receiver가 데이터를 시스템 버퍼에 저장할 수 없게 된 횟수

ignored: 내부버퍼가 없어 인터페이스에 인입된 패킷을 drop한 횟수,시스템 버퍼와는 다름,broadcast storm이나 noise 때문에 발생할 수 있음

abort: 수신한 frame의 일련번호가 잘못되었을 때 발생

dribble condition detected: frame에 bit에러가 주기적으로 발생할 경우,frame은 처리됨

underruns: 장비가 처리할 수 있는 용량보다 transmitter가 빠르게 보낸 횟수

output errors: 전송되지 못하고 버려진 패킷수,네트웍 트래픽이 과부하가 될 때 발생

collisions: collision이 발생한 후 정상적으로 전송된 frame수

interface resets: 인터페이스가 reset된 횟수

babbles: 1518byte보다 큰 frame이 전송된 횟수

late collisions: 인터페이스가 frame을 전송하기 시작한 후 발생한 collision 수

deferred: media가 busy상태에서 기다린 다음 전송에 성공한 frame수

lost carrier: 캐리어를 잃어버린 횟수

no carrier: 캐리어가 없었던 횟수


영어 원문

Table 28 show interfaces ethernet Field Descriptions 

Field
Description

Ethernet ... is up
...is administratively down

Indicates whether the interface hardware is currently active and if it has been taken down by an administrator. "Disabled" indicates the router has received over 5000 errors in a keepalive interval, which is 10 seconds by default.

line protocol
is {up | down |
administratively down}

Indicates whether the software processes that handle the line protocol believe the interface is usable (that is, whether keepalives are successful) or if it has been taken down by an administrator.

Hardware

Hardware type (for example, MCI Ethernet, SCI, cBus Ethernet) and address.

Internet address

Internet address followed by subnet mask.

MTU

Maximum Transmission Unit of the interface.

BW

Bandwidth of the interface in kilobits per second.

DLY

Delay of the interface in microseconds.

rely

Reliability of the interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over 5 minutes.

load

Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.

Encapsulation

Encapsulation method assigned to interface.

ARP type:

Type of Address Resolution Protocol assigned.

loopback

Indicates whether loopback is set or not.

keepalive

Indicates whether keepalives are set or not.

Last input

Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.

output

Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.

output hang

Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.

Last clearing

Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.

*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.

Output queue, input queue, drops

Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.

Five minute input rate,
Five minute output rate

Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).

The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.

packets input

Total number of error-free packets received by the system.

bytes input

Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.

no buffers

Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.

Received ... broadcasts

Total number of broadcast or multicast packets received by the interface.

runts

Number of packets that are discarded because they are smaller than the medium's minimum packet size. For instance, any Ethernet packet that is less than 64 bytes is considered a runt.

giants

Number of packets that are discarded because they exceed the medium's maximum packet size. For example, any Ethernet packet that is greater than 1,518 bytes is considered a giant.

input error

Includes runts, giants, no buffer, CRC, frame, overrun, and ignored counts. Other input-related errors can also cause the input errors count to be increased, and some datagrams may have more than one error; therefore, this sum may not balance with the sum of enumerated input error counts.

CRC

Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data.

frame

Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a LAN, this is usually the result of collisions or a malfunctioning Ethernet device.

overrun

Number of times the receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.

ignored

Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be increased.

input packets with dribble condition detected

Dribble bit error indicates that a frame is slightly too long. This frame error counter is incremented just for informational purposes; the router accepts the frame.

packets output

Total number of messages transmitted by the system.

bytes

Total number of bytes, including data and MAC encapsulation, transmitted by the system.

underruns

Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.

output errors

Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, as some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.

collisions

Number of messages transmitted due to an Ethernet collision. A packet that collides is counted only once in output packets.

interface resets

Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.

restarts

Number of times a Type 2 Ethernet controller was restarted because of errors.

babbles

The transmit jabber timer expired.

late collision

Number of late collisions. Late collision happens when a collision occurs after transmitting the preamble. The most common cause of late collisions is that your Ethernet cable segments are too long for the speed at which you are transmitting.

deferred

Deferred indicates that the chip had to defer while ready to transmit a frame because the carrier was asserted.

lost carrier

Number of times the carrier was lost during transmission.

no carrier

Number of times the carrier was not present during the transmission.

output buffer failures

Number of failed buffers and number of buffers swapped out.

'IT > 네트워크' 카테고리의 다른 글

국가별 사용 IP대역 알아내기  (1) 2009.06.05
XP ipconfig 명령 사용법  (0) 2009.06.03
cisco장비 인터페이스 정보들  (0) 2009.05.21
cisco configuration register  (0) 2009.05.21
FTP의 Passive-mode  (0) 2009.05.21
sFlow 와 Netflow  (0) 2009.05.19
Posted by novice9

댓글을 달아 주세요

이전버튼 1 이전버튼

블로그 이미지
이 블로그는 삽질을 기록하는 곳입니다. ^_^
novice9
텍스트큐브,티스토리 검색

달력

 « |  » 2018.08
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

최근에 받은 트랙백

글 보관함

Yesterday15,250
Today4,141
Total4,253,498