Technical data
Step 3—Configuring the Ethernet Interface
Dial Solutions Quick Configuration Guide
3-8
Ethernet0 10.1.4.1 YES manual up up
Serial0 unassigned YES unset administratively down down
In the next example, notice that the status is up but the protocol is down. The following logging
message appears at 00:40:20: “Unit 0, lost carrier. Transceiver problem?.”After the
administrator plugs the Ethernet cable into the Ethernet port, the interface comes up.
See 00:40:25.
robo-austin# show ip interface brief
Interface IP-Address OK? Method Status Protocol
BRI0 unassigned YES unset administratively down down
BRI0:1 unassigned YES unset administratively down down
BRI0:2 unassigned YES unset administratively down down
Ethernet0 10.1.4.1 YES manual up down
Serial0 unassigned YES unset administratively down down
robo-austin#
00:40:20: %QUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver problem?
00:40:25: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed sta
te to up
robo-austin#
• Establish connectivity with an Ethernet-based device. In this example, IP address 10.1.4.2 is
assigned to the first external PC on this LAN to test for router-to-PC connectivity. The PC’s DOS
prompt application is opened and the ping 10.1.4.1 command is issued.
Microsoft(R) Windows 95
(C)Copyright Microsoft Corp 1981-1996.
C:\WINDOWS> ping 10.1.4.1
Pinging 10.1.4.1 with 32 bytes of data:
Reply from 10.1.4.1: bytes=32 time=3ms TTL=236
Reply from 10.1.4.1: bytes=32 time=2ms TTL=236
Reply from 10.1.4.1: bytes=32 time=3ms TTL=236
Reply from 10.1.4.1: bytes=32 time=2ms TTL=236
• Try pinging the PC from the Cisco 1604. If the PC has not yet used any IP services or drivers,
you might get a failure. The preferred method is to ping the router from a PC on the LAN first.
robo-austin# ping 10.1.4.2
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.4.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 4/5/8 ms
• If you know that the Ethernet interface is up but not performing correctly, enter the show
interface ethernet 0 command. This example shows errors in the counters, because the Ethernet
cable was not plugged in.
robo-austin# show interface ethernet 0
Ethernet0 is up, line protocol is up
Hardware is QUICC Ethernet, address is 0060.834f.6626 (bia 0060.834f.6626)
Internet address is 10.1.4.1/24
MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 234/255, load 1/255
Encapsulation ARPA, loopback not set, keepalive set (10 sec)
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:08, output 00:00:04, output hang never
Last clearing of "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
2 packets input, 644 bytes, 0 no buffer