Article View: comp.dcom.sys.cisco
Article #1886FDDI board refuses to work, 100% cpu load to boot
From: Hans van Staveren
Date: Thu, 07 Jan 1993 17:58
Date: Thu, 07 Jan 1993 17:58
109 lines
5309 bytes
5309 bytes
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
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.
Here is some other data: if this means anything to more experienced
FDDI customers I would be much appreciated.
colossus#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
System Bootstrap, Version 4.3(5)
colossus uptime is 36 minutes
System restarted by power-on
Running default software
CSC3 (68020) processor with 4096K bytes of memory.
1 cBus controller.
6 Ethernet/IEEE 802.3 interface.
1 FDDI network interface.
Environmental Controller.
64K bytes of multibus memory.
64K bytes of non-volatile configuration memory.
Configuration register is 0x101
colossus#show controller cbus
cBus 0, controller type 3.0, microcode version 2.0
128 Kbytes of main memory, 32 Kbytes cache memory
Restarts: 0 line down, 0 hung output, 0 controller error
MEC 0, controller type 5.1, microcode version 2.2
Interface 0 is Ethernet0, station address 0000.0c01.c806
10 buffer RX queue threshold, 13 buffer TX queue limit
Transmitter delay is 0 microseconds
Interface 1 is Ethernet1, station address 0000.0c01.c807
10 buffer RX queue threshold, 13 buffer TX queue limit
Transmitter delay is 0 microseconds
Interface 2 is Ethernet2, station address 0000.0c01.c808
10 buffer RX queue threshold, 13 buffer TX queue limit
Transmitter delay is 0 microseconds
Interface 3 is Ethernet3, station address 0000.0c01.c809
10 buffer RX queue threshold, 13 buffer TX queue limit
Transmitter delay is 0 microseconds
Interface 4 is Ethernet4, station address 0000.0c01.c80a
10 buffer RX queue threshold, 13 buffer TX queue limit
Transmitter delay is 0 microseconds
Interface 5 is Ethernet5, station address 0000.0c01.c80b
10 buffer RX queue threshold, 13 buffer TX queue limit
Transmitter delay is 0 microseconds
--More--
FDDI 2, controller type 4.0, microcode version 1.0
Interface 12 is Fddi0, station address 0000.0c02.1076
6 buffer RX queue threshold, 5 buffer TX queue limit
colossus#show controller fddi
Fddi0 - hardware version 4.0, microcode version 1.0
Phy-A registers:
cr0 2, cr1 0, cr2 0, status 4, cr3 0
Phy-B registers:
cr0 2, cr1 0, cr2 0, status 4, cr3 0
FORMAC registers:
irdtlb FC84, irdtneg FFFF, irdmir FFFFFFFF, irdthtt 8A8A
irdtrth FA94, irdtmax FBC5, irdtvxt 0085, irdstmc 0418
irdmode 0000, irdimsk 0000, irdstat 0080, irdtpri 0000
FDDI registers:
tx_current 0000, tx_pending 0000, tx_restore 0000, tx_clbn 015A
tx_pen_ofst 0000, tx_pen_cnt 0, tx_pen_type 0000, tx_start_cnt 8000
rx_current 2504, rx_pending 3FA4, rx_recvd 0000, rx_free 00EE
rx_flags 0000, rx_error 00FA, rx_limit 4496, rx_word_offset 22
hold_reg 0001, clm_bn_flg 0000, enable 0001, fsvld 0000
lstinc 0, errinc 0, mss_frm 0, frinc 0, phy-a 0018, lem_a 1
fr_int_cnt 0, xtmabti 0, frmcpd 3, eof 3, phy-b 0018, lem_b 9121
claim 0, beacon 0, async_reg 0, async 0, stat_mask 0100
sync_req 0, sync 0, tx_state 0000, int_stat 0000
colossus#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
0 transitions
Technical Details
Message-ID:
<C0HwL1.8qr@cs.vu.nl>Path:
arc1-ca.pugleaf.net!sparky!uunet!mcsun!sun4nl!star.cs.vu.nl!saterShow Full Headers
Complete Article Headers
Newsgroups: comp.dcom.sys.cisco Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!sun4nl!star.cs.vu.nl!sater From: sater@cs.vu.nl (Hans van Staveren) Subject: FDDI board refuses to work, 100% cpu load to boot Message-ID: <C0HwL1.8qr@cs.vu.nl> Sender: news@cs.vu.nl Organization: Fac. Wiskunde & Informatica, VU, Amsterdam Date: Thu, 7 Jan 1993 17:58:10 GMT Lines: 109