Routers daily maintenance and scheduling errors

Usually we use the show interface command to view the information of the interface, such as show interface gig 1/0, or shown int pos 2/0, to view the port information of the router's thousand Gigabit Ethernet interface and the POS interface respectively.

To view the Ethernet interface information, use the command on 7507: show Interfaces fastethernet [Slot/port-adapter/port]

To view the POS interface information, use the command on 7507: show Interfaces pos [Slot/port-adapter/port]

1. The following example shows the interface configuration information for the 1th Fast Ethernet interface on the 1th PA on the 1th slot on the 7507 view:

router# Show Interfaces FastEthernet 1/0/0

Fast ethernet1/0/0 is up, line protocol are up

Hardware is Tswitch, the address is 00e0.f7a4.5130 (BIA 00e0.f7a4.5130)

MTU 1500 bytes, BW 100000 kbit, DLY usec, rely 255/255, load 1/255

Encapsulation ARPA, loopback not set, KeepAlive set (SEC)

Half-duplex, 100BaseTX

ARP Type:arpa, ARP Timeout 04:00:00

Last input 00:05:30, output 00:00:00, output hang never

Last clearing of the "show interface" counters never

Queueing Strategy:fifo

Output queue 0/40, 0 drops; Input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

312 packets Input, 18370 bytes, 0 no buffer

Received 216 broadcasts, 0 runts, 0 giants, 0 throttles

3 input errors, 0 CRC, 0 frame, 0 overrun, 3 ignored, 0 abort

0 input packets with dribble condition detected

15490 packets output, 1555780 bytes, 0 underruns

2 output errors, 0 collisions, 2 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier

2 output buffer failures, 0 output buffers swapped out

2. The following example shows the interface configuration information for the 1th Fast Ethernet interface on the 1th PA on the 2nd slot on the 7507 view:

router# Show Interfaces Pos 2/0/0

Pos2/0/0 is up, line protocol are up

Hardware is Cybus Packet over Sonet

DESCRIPTION:PRI-T1 NET to Zippy (4K) to Pac-bell

Internet address is 10.1.1.1/27

MTU 4470 bytes, BW 1000 kbit, DLY 40000 usec, rely 255/255, load 1/255

Encapsulation HDLC, loopback not set, KeepAlive set (3 sec)

Last input 00:00:00, output 00:00:00, output hang never

Last clearing of "show interface" counters 00:23:09

Queueing Strategy:fifo

Output queue 0/40, 0 drops; Input queue 0/75, 0 drops

5 minute input rate 0 bits/sec, 1 packets/sec

5 minute output Rate 1000 bits/sec, 1 packets/sec

1046 packets input, 54437 bytes, 0 no buffer

Received 485 broadcasts, 0 runts, 0 giants, 0 parity

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort

4013 packets output, 1357412 bytes, 0 underruns

0 output errors, 0 applique, 0 interface resets

0 output buffer failures, 0 output buffers swapped out

0 carrier Transitions

3. The following gives the specific meaning of all the table entries in the output of show interface:

Fast Ethernet ... is up

. is administratively down

Indicates whether the hardware of the interface is currently activated or is showdown by the administrator manually.

Line protocol is

The line protocol that identifies the interface is whether the software process is available or is manually given to shutdown by the administrator.

Hardware

Hardware types (e.g. MCI Ethernet, SCI, Cbus Ethernet) and hardware addresses

Internet Address

The IP address of this interface with subnet information.

Mtu

The maximum transmission unit on the interface.

Bw

The bandwidth of the interface, usually the unit is kb/s.

DLY

The delay of the port, the unit is Ms.

Rely

The reliability parameters of the interface with a 255 reference number (255/255 is absolutely reliable) are calculated in 5-minute averages.

Load

The load (255/255 is the absolute load) of the interface with a reference number of 255, and the average of 5 minutes is computed.

Encapsulation

The package type of the interface.

ARP type

The type of Address Resolution Protocol (ARP) for the interface configuration.

Loopback

Identifies whether an interface loop is set.

KeepAlive

Identifies whether the interface has set up send Alive (keepalives) information

Last input

The time since the interface received the most recent packet. The counter is updated when the packet is forwarded by Precess-switch, and the counter is not updated when the packet is forwarded in a fast-switch manner.

Output

The time since the interface sent the most recent packet.

Output Hang

Interface is displayed as never if there is no reboot due to the time that the packet was restarted because of the long packet transmission time.

Last clearing

Clears the time after the interface statistic counter. Note: The variable information that may affect the route will not be purged from 0, such as load and reliablity

The model * * * indicates that the time after the calculator is too long to show.

Output queue, input queue, drops

The number of packets in the input output queue in the interface. Each number is followed by the maximum range of a/queue. and the number of packets discarded that exceed the maximum range of the queue.

5 minute input rate,

5 minute output rate

Average of packets transmitted per second in the last 5 minutes.

Packets Input

The total number of packets received by the system.

bytes

The number of bytes in all packets (including data and Mac encapsulation) that the system receives.

No buffer

Because there is not enough cache in the system to discard the number of packets. Can be compared with the ignore count. The poor quality of the Ethernet last broadcast storm and the serial interface may often result in an increase in the counter.

Received ... broadcasts

The number of broadcast and multicast packets received by the interface.

Runts

The number of packets dropped because they are less than the minimum packet size of the media. For example, for Ethernet, packets less than 64byte are considered to be a runt.

Giants

The number of packets dropped because they are larger than the maximum packet size of the media. For example, for Ethernet, packets larger than 1518byte are considered to be a runt.

Throttles

The number of interfaces disable may be due to factors such as caching or processor overload.

Input errors

Includes all counters for runts, giants, no buffer, CRC, frame, overrun, and ignored. Other and input-related error packs can also cause the input errors counter to grow. At the same time, a packet may include multiple error.

Crc

The number of cyclic redundancy checksums that the interface receives. In the local area network, usually because of the quality of the line or hardware transmission problems, a relatively high number of CRC is usually some workstation sent a large number of bad packets caused.

Frame

The number of decimal packets that are received with CRC errors and non integers, usually in the LAN, because of collisions or failures of Ethernet devices.

Overrun

Because the rate of input exceeds the processing power of the recipient's hardware, the number of times the hardware cache is not processed.

Ignored

Unlike the system's cache, this is the number of packets ignored due to an internal cache of interfaces.

Abort

The number of packets interrupted while accepting.

Input packets with dribble condition detected

Frame is an extra long input packet.

Packets Output

The number of packets sent by the system.

bytes

The number of bytes in all packets (including data and Mac encapsulation) that are sent by the system.

Underruns

The number of times that the sender's transmission is too fast causing the router to be unable to process.

Output errors

The sum of all errors that the interface considers to transmit packets, while a packet may include multiple error.

Collisions

The number of retransmission packets due to an Ethernet conflict.

Interface resets

The number of times the interface has been restarted. This can happen if packets entering the queue are not transmitted in a matter of seconds. On the serial interface, it is possible that the transmission of the modem fault does not send a clock signal or cable problems. If the system finds that the interface is down because of the carrier signal interface up but the protocol is down, the interfaces will try to restart themselves periodically. Interfaces can also be restarted when the interface loops or is shut down.

Babbles

The transmitting timer to.

Late collision

The collision that occurs after the preamble header of the packet is transmitted is called late collisions. The late collision usually occurs because the ethernet cable is too long, exceeding the distance limit it can transmit.

Deferred

Because of the carrier problem, the chip delays transmission frames.

Lost Carrier

The number of times the carrier was lost during transmission.