| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
Last Saturday, my customer found the following sequence of messages on
his console.
What do the lines with '<<<<' mean (fta0: Halted, fta0: PC Trace, etc.)
mean?
Please, also, note that after attempting the reboot, the INIT sequence
hung at or after "RESET_TC" for about 3 minutes before the system
manager cycled the power switch. After cycling the power, the system
booted up just fine. Any comments on this?
13-Apr-1996 11:59:45 fta0: PC Trace received <<<<
13-Apr-1996 14:23:10 fta0: Ring beacon initiated
13-Apr-1996 14:23:10 fta0: Elasticity buffer error
13-Apr-1996 14:23:10 fta0: Elasticity buffer error
13-Apr-1996 14:23:11 fta0: Link Unavailable.
13-Apr-1996 14:23:11 fta0: Elasticity buffer error
13-Apr-1996 14:23:12 fta0: Elasticity buffer error
13-Apr-1996 14:23:13 fta0: Elasticity buffer error
13-Apr-1996 14:23:14 fta0: Elasticity buffer error
13-Apr-1996 14:23:15 fta0: Elasticity buffer error
13-Apr-1996 14:23:16 fta0: Halted. <<<<
13-Apr-1996 14:23:17 fta0: Halt Reason: PC Trace <<<<
13-Apr-1996 14:23:17 fta0: Link Unavailable.
13-Apr-1996 14:23:19 fta0: Link Available.
13-Apr-1996 14:23:21
13-Apr-1996 15:03:43
13-Apr-1996 15:03:43 Digital UNIX Version V3.2 (pt9500.ped.pto.ford.com) conso>
13-Apr-1996 15:03:43
13-Apr-1996 15:03:43 login: root
13-Apr-1996 15:05:27 Password:
13-Apr-1996 15:05:29 Last login: Sat Apr 13 11:43:51 from pt9548.ped.pto.f
13-Apr-1996 15:05:29
13-Apr-1996 15:05:29 Digital UNIX V3.2D-1 (Rev. 41); Sun Mar 31 17:40:58 EST 1>
13-Apr-1996 15:05:29 Digital UNIX V3.2D-1 Worksystem Software (Rev. 41)
13-Apr-1996 15:05:30 [root]pt9500:/> fta0: Link Unavailable.
13-Apr-1996 15:35:25 fta0: Link Available.
13-Apr-1996 15:36:12 fta0: Link Unavailable.
13-Apr-1996 15:36:49 fta0: Link Available.
13-Apr-1996 15:38:58 [root]pt9500:/>
13-Apr-1996 15:38:58 [root]pt9500:/>
13-Apr-1996 15:38:59 [root]pt9500:/>
13-Apr-1996 15:38:59 [root]pt9500:/> reboot
13-Apr-1996 15:39:10 Apr 13 15:39:10 automount[339]: exiting
13-Apr-1996 15:39:10 syncing disks... 1 done
13-Apr-1996 15:39:30 rebooting.... (transferring to monitor)
13-Apr-1996 15:39:30
13-Apr-1996 15:39:30
13-Apr-1996 15:39:30 83 BOOT SYS
13-Apr-1996 15:39:30 INIT-S-CPU...
13-Apr-1996 15:39:30 INIT-S-RESET_TC...
13-Apr-1996 15:42:43
13-Apr-1996 15:42:43 DEC 3000 - M900
13-Apr-1996 15:42:44 Digital Equipment Corporation
13-Apr-1996 15:42:44 System conducting power up tests
13-Apr-1996 15:42:44
---------------------------------------------------------
13-Apr-1996 15:42:44
13-Apr-1996 15:42:44 Devnam Devstat
13-Apr-1996 15:42:44 -------- -------
13-Apr-1996 15:42:44 CPU OK KN17-AB-V5.1-S747-I19D-sV2.1-DECchi>
13-Apr-1996 15:42:45 OSC 275 MHz
13-Apr-1996 15:42:45 ASIC OK
13-Apr-1996 15:42:45 MEM OK 256MB
13-Apr-1996 15:42:54 NVR OK
13-Apr-1996 15:42:54 SCC ?? 003 0050 ptr(0) = Not Present keybd>
13-Apr-1996 15:42:54 NI OK Ethernet Address: 08-00-2B-94-86-65 >
13-Apr-1996 15:42:54 SCSI OK
13-Apr-1996 15:43:01 ISDN OK
13-Apr-1996 15:43:03 TC5 OK - PMAF-FS
13-Apr-1996 15:43:10 TC4 OK - PMTNV-AA
13-Apr-1996 15:43:26 TC3 OK - KZTSA-AA
13-Apr-1996 15:43:28 TC2 OK - KZTSA-AA
13-Apr-1996 15:43:30 TC1 OK - KZTSA-AA
13-Apr-1996 15:43:33 TC0 OK - PMAZC-AA
13-Apr-1996 15:43:42
---------------------------------------------------------
13-Apr-1996 15:43:42 System power up tests detected error(s).
13-Apr-1996 15:43:42 See your system documentation for more information.
13-Apr-1996 15:43:43
13-Apr-1996 15:43:43 >>> boot
13-Apr-1996 15:43:49 INIT-S-CPU...
13-Apr-1996 15:43:49 INIT-S-RESET_TC...
13-Apr-1996 15:43:50 INIT-S-ASIC...
13-Apr-1996 15:43:50 INIT-S-MEM...
13-Apr-1996 15:43:53 INIT-S-NVR...
13-Apr-1996 15:43:53 INIT-S-SCC...
Thanks!
Stu
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2012.1 | NPSS::TAYLOR | Tue Apr 16 1996 19:36 | 32 | ||
I'm no expert but I got 2 cents and hopefully a helping hand to get this
started.
PC Trace is the process fddi stations use to recover from a major fault
on the ring. Look at note 1203 for a description of PC_trace. PC_Trace
is a serious event, it should not happen.
This station's downstream neighbor traced this station twice, I'm assuming
that the log is not complete. I'd also assume if nothing is done it's
going to happen again. The fta device firmware halted because of the
trace.
I'd try to understand what caused the elasticity buffer errors. Someone
just happened to mention that elasticity buffer errors could be attributed
to someone's clocks out of spec. What's this system connected to?
On the reboot, it looks like it's still having a problem with the ring.
Why was it rebooting 40 minutes after the last pc_trace?
13-Apr-1996 15:05:30 [root]pt9500:/> fta0: Link Unavailable.
13-Apr-1996 15:35:25 fta0: Link Available.
13-Apr-1996 15:36:12 fta0: Link Unavailable.
13-Apr-1996 15:36:49 fta0: Link Available.
Do you know what this was refering to?
13-Apr-1996 15:43:42 System power up tests detected error(s).
13-Apr-1996 15:43:42 See your system documentation for more information.
| |||||
| 2012.2 | OHFSS1::FULLER | Never confuse a memo with reality | Tue Apr 30 1996 15:48 | 40 | |
Sorry for the delay in responding.
>This station's downstream neighbor traced this station twice,
Yep, that's what my copy of Raj Jain's "FDDI Handbook" says (I went out
and bought it between then and now).
>What's this system connected to?
This system, and all the other systems here are connected to a
Synoptics "Lattis Net" concentrator. Sorry, I don't have a model
number at hand.
>On the reboot, it looks like it's still having a problem with the ring.
>Why was it rebooting 40 minutes after the last pc_trace?
This system is a file server to 50 other systems. It was rebooted due
to lack of service to the other systems, and it took use 30 minutes to
get to it (on a weekend, etc).
>13-Apr-1996 15:36:12 fta0: Link Unavailable.
>13-Apr-1996 15:36:49 fta0: Link Available.
>
>Do you know what this was refering to?
Typically, whenever a system boots or shuts down, we get these. I
figured it was a new system coming onto, or one going off, the ring
causing it.
>13-Apr-1996 15:43:42 System power up tests detected error(s).
This is due to no keyboard/mouse connected to the 3000/900 workstation
being used as a file server.
Thanks!
Stu
| |||||