|
|
The Fast Ethernet network interface module (NIM) for the Cisco 4000 series routers provides a single full-duplex, 100-Mbps Ethernet interface. This interface conforms with the IEEE 802.3u Fast Ethernet specification, which ensures multivendor interoperability.
The Fast Ethernet NP-1FE Module has the following benefits:
The following routers support the Fast Ethernet NP-1FE Module:
Only two high-speed interfaces should be installed in the Cisco 4500-M or Cisco 4700-M router. This means that only two Fast Ethernet interfaces or one Fast Ethernet interface in combination with an ATM or FDDI interface is supported in the Cisco 4700 or the Cisco 4500 router.
Support for the 100 Mbps Fast Ethernet interface is supplied on the Cisco 4500 and Cisco 4700 routers, a Fast Ethernet network processor module (NPM).
Use the show interface fastethernet command to display interface statistics, and use the show controller fastethernet to display the information about the Fast Ethernet controller chip. The output shows information about the initialization block, transmit ring, receive ring, and errors.
Perform the tasks in the following sections to configure a Fast Ethernet interface.
To specify an Ethernet interface and enter interface configuration mode, perform the following task in global configuration mode:
| Task | Command |
|---|---|
| Begin interface configuration for the Cisco 4000 series with a Fast Ethernet NIM installed. | interface fastethernet number |
Use the show interfaces fastethernet command to display the Fast Ethernet slots and ports. The Fast Ethernet NIM and the FEIP default to half-duplex mode.
Currently, there are three common Ethernet encapsulation methods:
The encapsulation method you use depends upon the type of Ethernet media connected to the router or access server and the routing or bridging application you configure. Establish Ethernet encapsulation by performing one of the following tasks in interface configuration mode:
| Task | Command |
|---|---|
| Select ARPA Ethernet encapsulation. | encapsulation arpa |
| Select SAP Ethernet encapsulation. | encapsulation sap |
| Select SNAP Ethernet encapsulation. | encapsulation snap |
You can specify that the Ethernet network interface module (NIM) on the Cisco 4000 uses either an AUI and a 15-pin connector or 10BaseT and an RJ-45 connector. To do so, perform one of the following tasks in interface configuration mode:
| Task | Command |
|---|---|
| Select a 15-pin Ethernet connector. | media-type aui |
| Select an RJ-45 Ethernet connector. | media-type 10baset |
To clear the interface counters shown with the show interfaces command, enter the following command at the EXEC prompt:
| Task | Command |
|---|---|
| Clear interface counters for the Fast Ethernet NIM on the Cisco 4000 series routers. | clear counters fastethernet number |
The command clears all the current interface counters from the interface unless the optional arguments are specified to clear only a specific interface type from a specific slot and port number.
Complete the following tasks in EXEC mode to clear and reset interfaces. Under normal circumstances, you do not need to clear the hardware logic on interfaces.
| Task | Command |
|---|---|
| Reset the hardware logic on an interface. | clear interface fastethernet number |
| Reset the hardware logic on an asynchronous serial line. | clear line [number]1 |
| Clear the entire Token Ring RIF cache. | clear rif-cache |
 | Caution Do not use this test to diagnose problems with an operational server. |
To test the status of the Fast Ethernet interface, perform the following task on a nonoperational server in privileged EXEC mode:
| Task | Command |
|---|---|
| Check the network interface. | test interface fastethernet |
For an example of how to configure the Fast Ethernet interface, refer to the Installing Fast Ethernet Network Processor Modules in the Cisco 4000 Series document.
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 11.2 Configuration Fundamentals Command Reference.
To reset the controller for a specified Fast Ethernet interface, use the clear interface fastethernet privileged EXEC command.
clear interface fastethernet number (Cisco 4500 and Cisco 4700)Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
The following example resets the controller for the Fast Ethernet 0 interface on a Cisco 4500:
clear interface fastethernet 0
To select a particular Fast Ethernet interface for configuration, use the interface fastethernet privileged EXEC command.
interface fastethernet number (Cisco 4500 and Cisco 4700)Standard Advanced Research Projects Agency (ARPA) encapsulation is configured.
Privileged EXEC
This command first appeared in Cisco IOS Release 11.2.
The following example configures Fast Ethernet interface 0 for standard ARPA encapsulation
(the default setting) on a Cisco 4500 or Cisco 4700 router:
interface fastethernet 0
show interfaces fastethernet
To display information about initialization block information, transmit ring, receive ring and errors for the Fast Ethernet controller chip on the Cisco 4500 and Cisco 4700, use the show controllers fastethernet EXEC command.
show controllers fastethernet number (Cisco 4500 and Cisco 4700)| number | On a Cisco 4500 or Cisco 4700 router, specifies the NPM number. The number is assigned at the factory at the time of installation or when added to a system. |
EXEC
This command first appeared in Cisco IOS Release 11.2.
The output of this command is generally useful for diagnostic tasks performed by technical support only.
The following is sample output from the show controllers fastethernet command on a Cisco 4500 router:
c4500-1# show controllers fastethernet 0
DEC21140 Slot 0, Subunit 0
dec21140_ds=0x60001234, registers=0x3c001000, ib=0x42301563, ring entries=256
rxring=0x40235878, rxr shadow=0x64528745, rx_head=0, rx_tail=10
txring=0x43562188, txr shadow=0x65438721, tx_head=17, tx_tail=34, tx_count=17
DEC21140 Registers
CSR0=0x23457667, CSR3=0x12349878, CSR4=0x34528745, CSR5=0x76674565
CSR6=0x76453676, CSR7=0x76456574, CSR8=0x25367648, CSR9=0x87253674
CSR11=0x23456454, CSR12=0x76564787, CSR15=0x98273465
DEC21140 PCI registers
bus_no=0, device_no=0
CFID=0x12341234, CFCS=0x76547654, CFRV=0x87658765, CFLT=0x98769876
CBIO=0x12344321, CBMA=0x23454321, CFIT=0x34567654, CFDA=0x76544567
MII registers
Register 0x00: 0x1234 0x1234 0x2345 0x3456 0x4567 0x5678 0x6789 0x7890
Register 0x08: 0x9876 0x8765 0x7654 0x6543 0x5432 0x4321 0x3210 0x2109
Register 0x10: 0x1234 0x2345 0x3456 0x4567 0x5678 0x6789 0x7890
Register 0x18: 0x9876 0x8765 0x7654 0x6543 0x5432 0x4321
DEC21140 statistics
filtered_in_sw=1000, throttled=10, enabled=10
rx_fifo_overflow=10, rx_no_enp=12, rx_late_collision=18
rx_watchdog=15, rx_process_stopped=15, rx_buffer_unavailable=1500
tx_jabber_timeout=10, tx_carrier_loss=2, tx_deffered=15
tx_no_carrier=1, tx_late_collision=10, tx_excess_coll=10
tx_process_stopped=1, fata_tx_err=0
show interfaces fastethernet
To display information about the Fast Ethernet interfaces, use the show interfaces fastethernet EXEC command.
show interfaces fastethernet [number] (Cisco 4500 and Cisco 4700)EXEC
This command first appeared in Cisco IOS Release 11.2.
The following is sample output from the show interface fastethernet command on a Cisco 4500 router:
c4500-1# show interfaces fastethernet 0
FastEthernet0 is up, line protocol is up
Hardware is DEC21140, address is 0000.0c0c.1111 (bia 0002.eaa3.5a60)
Internet address is 11.0.0.1 255.0.0.0
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive not set, hdx, 100BaseTX
ARP type: ARPA, ARP Timeout 4:00:00
Last input never, output 0:00:16, output hang 0:28:01
Last clearing of "show interface" counters 0:20:05
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
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 1786161921 ignored, 0 abort
0 watchdog, 0 multicast
0 input packets with dribble condition detected
67 packets output, 8151 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets, 0 restarts
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Table 1 describes these fields.
| Field | Description |
|---|---|
| FastEthernet0 is up... ...is administratively down | Indicates whether the interface hardware is currently active or if it has been taken down by an administrator. |
| line protocol is up ... is administratively down | Indicates whether the software processes that handle the line protocol consider the line usable 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. |
| output | Number of hours, minutes, and seconds since the last packet was successfully transmitted by the interface. Useful for knowing when a dead interface failed. |
| 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. |
| 5 minute input rate, 5 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 | Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system. |
| no buffer | Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets 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 errors | 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. |
| abort | Number of packets whose receipt was aborted. |
| watchdog | Number of times watchdog receive timer expired. It happens when receiving a packet with length greater than 2048. |
| multicast | Number of multicast packets received. |
| 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 retransmitted due to an Ethernet collision. This is usually the result of an overextended LAN (Ethernet or transceiver cable too long, more than two repeaters between stations, or too many cascaded multiport transceivers). 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 either 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. |
| 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. |
To test the Fast Ethernet interface by pinging itself, use the test interface fastethernet EXEC command.
test interface fastethernet number (Cisco 4000 series only)| number | Port, connector, or interface card number. On a Cisco 4500 or Cisco 4700 router, specifies the NPM number. The numbers are assigned at the factory at the time of installation or when added to a system, and can be displayed with the show interfaces command. |
EXEC
This command first appeared in Cisco IOS Release 11.2.
This command sends pings from the specified interface to itself. Unlike the ping command, the test interface fastethernet command does not require the use of an IP address.
The following example tests a Fast Ethernet interface on a Cisco 4500:
test interface fastethernet 0
ping
For additional software configuration information for the Cisco 4000 series, refer to the following documents:
|
|