[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2235
  • Last Modified:

Cisco 1720 Ethernet0 Port status

I have configured the ports on our 1720 with ip addresses etc,  fastethernet0 is up and pingable but Ethernet0 is not.

here is what is shown when i run 'show interface ethernet0'

Ethernet0 is up, line protocol is down
  Hardware is PQUICC Ethernet, address is 0004.dd0c.017d (bia 0004.dd0c.017d)
  Internet address is 192.168.3.250/24
  MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec,
     reliability 128/255, txload 1/255, rxload 1/255
  Encapsulation ARPA, loopback not set
  Keepalive set (10 sec)
  Half-duplex, 10BaseT
  ARP type: ARPA, ARP Timeout 04:00:00
  Last input never, output 00:00:09, 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
     0 packets input, 0 bytes, 0 no buffer
     Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
     318 input errors, 0 CRC, 0 frame, 0 overrun, 318 ignored
     0 input packets with dribble condition detected
     318 packets output, 21258 bytes, 0 underruns(0/0/0)
     318 output errors, 0 collisions, 2 interface resets
     0 babbles, 0 late collision, 0 deferred
     319 lost carrier, 0 no carrier

and i get the error message "%PQUICC_ETHER-1-LOSTCARR: Unit 0, lost carrier. Transceiver problem?"

any idea what i need to do to enable the port?  also the 'FDX' light isn't lit.  I have tried using two different patch cables, and none of them make link lights.

thank you!!!!
0
dosle
Asked:
dosle
1 Solution
 
harbor235Commented:
Lots of errors and CRC input errors, do you have the right cable? IOs the cable good? how about the switch port settings, are they appropriate for the ethernet connection? 10M ? or is it set for 100M?

harbor235
0
 
dosleAuthor Commented:
The ethernet0 port was connected to a 100base-tx switch elsewhere, that was causing the problem.  connected it to a autosensing switch fixed the problem.  for once it was an easy solution.  thank you!
0

Featured Post

[Webinar] Cloud and Mobile-First Strategy

Maybe you’ve fully adopted the cloud since the beginning. Or maybe you started with on-prem resources but are pursuing a “cloud and mobile first” strategy. Getting to that end state has its challenges. Discover how to build out a 100% cloud and mobile IT strategy in this webinar.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now