HP Virtual Connect 8Gb 24-port Fibre Channel Module for c-Class BladeSystem User Manual

Page 111

Advertising
background image

Command line 111

Name

RFC

Description

rfc1213_IpInHdrErrors

1213

The number of input datagrams discarded due to errors in the IP

header. Possible errors include bad checksums, version number
mismatches, format errors, time-to-live exceeded, errors discovered

while processing IP options, and so on.

rfc1213_IpInReceives

1213

The total number of input datagrams received from interfaces, including

datagrams received in error

rfc1493_Dot1dBasePort

DelayExceededDiscards

1493

The number of frames discarded by this port due to an excessive transit

delay through the bridge (incremented by both transparent and source

route bridges)

rfc1213_Dot1dBasePort
MtuExceededDiscards

1493

The number of frames discarded by this port due to excessive size
(incremented by both transparent and source route bridges)

rfc1213_Dot1dPortIn

Discards

1493

The number of valid frames received that were discarded (filtered) by

the Forwarding Process

rfc1213_Dot1dTpPortIn
Frames

1493

The number of frames received by this port from its segment. A frame
received on the interface that corresponds to this port is only counted by

this object if it is for a protocol being processed by the local bridging

function, including bridge management frames.

rfc1757_StatsBroadcast
Pkts

1757

The number of good packets received during the sampling interval that
were directed to the broadcast address

rfc1757_StatsCRCAlign

Errors

1757

The total number of packets received with a length of between 64 and

1518 octets (excluding framing bits, but including FCS octets),

inclusive, but had either a bad FCS with an integral number of octets
(FCS Error) or a bad FCS with a nonintegral number of octets

(Alignment Error).

rfc1757_StatsCollisions

1757

The best estimate of the total number of collisions in this Ethernet
segment. The value returned depends on the location of the RMON

probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2)

of IEEE standard 802.3 states that a station must detect a collision, in

the receive mode, if three or more stations are transmitting
simultaneously. A repeater port must detect a collision when two or

more stations are transmitting simultaneously. Therefore, a probe

placed on a repeater port could record more collisions than a probe
connected to a station on the same segment.

Probe location plays a smaller role for 10BASE-T. Section 14.2.1.4

(10BASE-T) of IEEE standard 802.3 defines a collision as the
simultaneous presence of signals on the DO and RD circuits

(transmitting and receiving at the same time). A 10BASE-T station can

only detect collisions when it is transmitting. Therefore, probes placed
on a station and a repeater should report the same number of collisions.

An RMON probe inside a repeater should ideally report collisions

between the repeater and one or more other hosts (transmit collisions as
defined by IEEE 802.3k) plus receiver collisions observed on any coax

segments to which the repeater is connected.

rfc1757_StatsDropEvents 1757

The total number of events in which packets were dropped by the probe

due to a lack of resources. This represents the number of times the
condition was detected, which does not necessarily equal the number

of dropped packets.

Advertising