Article View: comp.dcom.sys.cisco
Article #1891Re: FDDI board refuses to work, 100% cpu load to boot
From: Pasha Quadri
Date: Thu, 07 Jan 1993 22:13
Date: Thu, 07 Jan 1993 22:13
67 lines
3147 bytes
3147 bytes
Hello Hans, > I just installed our first FDDI board in our Cisco, and surprise.. > it doesn't work. It looks like it cannot enter into the ring. I had it > installed at first in our ring with 3 Interphase FDDI boards, but when that > didn't work I tried looping back the Cisco to itself. Even that did not > work. I configured it: > interface fddi0 > ip address 130.37.16.1 255.255.255.0 > no shutdown > Loopback on FDDI is not supported in the version you are running. You need at least 9.1 and the new ucode. > The router is now very slow, the 'show proc' output shows that the PHY-A > and PHY-B processes take all the time. I did a shutdown on the interface > and the router is back to normal. > It is making an attempt to complete the CMT state machine. Please check the internal cabling between the applique and the FDDI card. Did you run a debug of fddi-cmt-events ? Did you see an increment in the interface resets counter ? #show hardware > GS Software (GS3-F), Version 8.2(7) > Copyright (c) 1986-1991 by cisco Systems, Inc. > Compiled Wed 13-Nov-91 17:45 by mlb > lossus#show int fddi0 > > Fddi 0 is down, line protocol is down > Hardware type is cBus Fddi, hardware address is 0000.0c02.1076 > Internet address is 130.37.16.1, subnet mask is 255.255.255.0 > MTU 4470 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255 > Encapsulation SNAP, loopback not set, keepalive not set > ARP type: SNAP, ARP Timeout 4:00:00 > Phy-A state is connect, neighbor is unk, cmt signal bits 08/00, status HLS > Brk 5257, Con 5257, Tra 0, Nxt 5254, Sig 0, Join 0, Vfy 0, Act 0 > Phy-B state is connect, neighbor is unk, cmt signal bits 20C/00, status HLS > Brk 5258, Con 5258, Tra 0, Nxt 5255, Sig 0, Join 0, Vfy 0, Act 0 > CFM is isolated, token rotation 5000 usec, ring not operational > Upstream neighbor 0000.0000.0000, downstream neighbor 0000.0000.0000 > Last input never, output never, output hang never > Output queue 0/40, 0 drops; input queue 0/75, 0 drops > Five minute input rate 0 bits/sec, 0 packets/sec > Five 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, 0 ignored, 0 abort > 0 packets output, 0 bytes > 0 output errors, 0 collisions, 4 interface resets, 0 restarts I have opened case number 45267. Please refer to this when you communicate to me on this problem. Regards Pasha Quadri Cisco Cust. Engg
Technical Details
Message-ID:
<726451242.25838@news.Colorado.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!gatech!usenet.ins.cwru.edu!agate!boulder!recnewsShow Full Headers
Complete Article Headers
Newsgroups: comp.dcom.sys.cisco Path: arc1-ca.pugleaf.net!sparky!uunet!zaphod.mps.ohio-state.edu!darwin.sura.net!gatech!usenet.ins.cwru.edu!agate!boulder!recnews From: Pasha Quadri <quadri@last-call.cisco.com> Subject: Re: FDDI board refuses to work, 100% cpu load to boot In-Reply-To: Your message of 7 Jan 93 17:58:10 GMT Message-ID: <726451242.25838@news.Colorado.EDU> Sender: news Date: 7 Jan 93 14:13:16 PST Approved: news X-Note1: message-id generated by recnews X-Note2: mail msgid was <CMM.0.90.2.726444796.quadri@last-call.cisco.com> Lines: 68