[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
1570.0. "SABLE, OSF 3.0, defea keeps bouncing" by CSC32::B_GRUBBS () Thu Feb 02 1995 17:53
<<< AOSG::USERC:[NOTES$LIBRARY]ALPHA_OSF_IFT.NOTE;1 >>>
-< DEC OSF/1 -- Please enter QAR's not notes for bugs >-
================================================================================
Note 8814.0 OSF 3.0, Sable MP, DEFEA keeps bouncing No replies
CSC32::B_GRUBBS 53 lines 2-FEB-1995 17:53
--------------------------------------------------------------------------------
Customer with two sables (2100/500MP), two cpus' each machine...
OSF V3.0, firmware 3.6, DEFEA firmware 2.3
The defea card keeps spewing out errors onto the console.
They've finally gone to isolating the two machines with a
Cisco router in a dual attached configuration but still get this
list of errors.
Any ideas? From the messages it looks like the link bounces
every few minutes.
thanks,
--Bert Grubbs
Colorado CSC
------------------------------------------------------------------------
28-JAN-1995 05:16:24.75 FILER fta0: Ring initialized.
28-JAN-1995 05:16:24.83 FILER fta0: LEM error monitor reject.
28-JAN-1995 05:16:24.91 FILER fta0: LEM error monitor reject.
28-JAN-1995 05:16:25.41 FILER fta0: Link Unavailable.
28-JAN-1995 05:16:27.41 FILER fta0: Flushing Transmit queue.
28-JAN-1995 05:16:28.41 FILER fta0: Link Available.
28-JAN-1995 05:20:31.71 FILER fta0: Ring initialized.
28-JAN-1995 05:20:32.41 FILER fta0: Ring initialized.
28-JAN-1995 05:21:20.41 FILER fta0: Link Unavailable.
28-JAN-1995 05:21:22.41 FILER fta0: Flushing Transmit queue.
28-JAN-1995 05:21:23.41 FILER fta0: Link Available.
28-JAN-1995 05:23:31.31 FILER fta0: Ring initialized.
28-JAN-1995 05:23:32.41 FILER fta0: Ring initialized.
28-JAN-1995 06:28:22.41 FILER fta0: Link Unavailable.
28-JAN-1995 06:28:24.41 FILER fta0: Flushing Transmit queue.
28-JAN-1995 06:29:08.93 FILER fta0: Ring initialized.
28-JAN-1995 06:29:09.92 FILER fta0: Ring initialized.
28-JAN-1995 06:30:22.41 FILER fta0: Link Unavailable.
28-JAN-1995 06:30:24.34 FILER fta0: Flushing Transmit queue.
28-JAN-1995 06:30:25.41 FILER fta0: Link Available.
28-JAN-1995 06:30:52.42 FILER fta0: Ring initialized.
28-JAN-1995 06:30:53.41 FILER
28-JAN-1995 06:31:34.34 FILER [49]filer:#
28-JAN-1995 06:31:35.41 FILER [49]filer:# fta0: Ring initialized.
28-JAN-1995 06:39:16.41 FILER fta0: Link Unavailable.
28-JAN-1995 06:39:18.41 FILER fta0: Flushing Transmit queue.
28-JAN-1995 06:39:19.41 FILER fta0: Link Available.
28-JAN-1995 06:46:36.41 FILER fta0: Ring initialized.
31-JAN-1995 06:56:47.39 FILER fta0: Ring initialized.
31-JAN-1995 06:56:48.41 FILER fta0: Link Unavailable.
31-JAN-1995 06:56:50.43 FILER fta0: Flushing Transmit queue.
31-JAN-1995 06:56:51.41 FILER fta0: Link Available.
31-JAN-1995 07:03:48.83 FILER fta0: Ring initialized.
T.R | Title | User | Personal Name | Date | Lines |
---|
1570.1 | | NETCAD::STEFANI | Welcome to the Revolution! | Thu Feb 02 1995 18:40 | 11 |
| >> They've finally gone to isolating the two machines with a
>> Cisco router in a dual attached configuration but still get this
>> list of errors.
Er, uh, use a DECnis instead? :-)
I don't know if you're going to tell too much from the console. You'll
likely need to put an FDDI analyzer on the network and see what's going
on. I agree that it looks like the link is bouncing.
/l
|