| 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 |
Could someone explain exactly what those messages mean and
wether they definitively don't show a problem ?
This is on Ultrix 4.2A, on DS5000-200 and 5000-240...
Thank's in advance and best regards !
Thierry A.
------------------------------------------------------
uerf version 4.2-011 (16)
********************************* ENTRY 1. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4185.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:16:52 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE fza0: Unsolicited Event ->
********************************* ENTRY 2. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4186.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:16:52 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE Ring Init Received
********************************* ENTRY 3. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4187.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:17:02 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE fza0: Unsolicited Event ->
********************************* ENTRY 4. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4188.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:17:02 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE Ring Init Received
********************************* ENTRY 5. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4189.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:17:12 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE fza0: Unsolicited Event ->
********************************* ENTRY 6. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4190.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:17:12 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE Ring Init Received
********************************* ENTRY 7. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4191.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:17:22 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE fza0: Unsolicited Event ->
********************************* ENTRY 8. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4192.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:17:22 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE Ring Init Received
********************************* ENTRY 9. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4193.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:18:22 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE fza0: Unsolicited Event ->
********************************* ENTRY 10. *********************************
----- EVENT INFORMATION -----
EVENT CLASS OPERATIONAL EVENT
OS EVENT TYPE 250. ASCII MSG
SEQUENCE NUMBER 4194.
OPERATING SYSTEM ULTRIX 32
OCCURRED/LOGGED ON Tue Mar 30 14:18:22 1993 MET DST
OCCURRED ON SYSTEM vsnhdb
SYSTEM ID x82020220 HW REV: x20
FW REV: x2
CPU TYPE: R2000A/R3000
PROCESSOR TYPE KN02/R3000
MESSAGE Ring Init Received
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 914.1 | CSC32::B_GOODWIN | Tue Mar 30 1993 08:45 | 3 | ||
What's the rest of your FDDI network look like? A station out on the FDDI is issuing ring inits. This can be caused by a number of reasons, from a station entering the ring to a faulty station. | |||||
| 914.2 | More details... | LEMAN::AGASSIS | Think Quality ! | Wed Mar 31 1993 05:17 | 30 |
Thank's for your fast reply.
Here is the original request :
"
We have 16 DECstation 5000/200 and 5000/240 connected via FDDI
(thinewire), to a DECconcentrator 500. The FDDI is isolated,
just for NFS, and Ethernet is independent of it.
The performance is good and we are satisfied.
However once in a while ALL 16 machines start receiving ring inits
(every 30 seconds), see error log above.
THis only ends when we power off/on the DECconcentrator.
I wonder what this means ?
"
I've asked my customer to connect a terminal on the OBM port to
watch the counters and to give us the FW level of the concentrator.
If it where just a station joining the network, we should get
one message/station, shouldn't we ?
In this case, once started, the errors come every 30 seconds until the
concentrator is restarted...
Any idea ?
Thank's again for your help and best regards !
Thierry A.
| |||||
| 914.3 | NETRIX::thomas | The Code Warrior | Wed Mar 31 1993 09:24 | 3 | |
When you turn off a machine (or reboot or turn the interface off or on), you disrupt the ring which forces the ring to be initialized. The ring init received is to be expected. | |||||
| 914.4 | Every 30 seconds ?? | LEMAN::AGASSIS | Think Quality ! | Wed Mar 31 1993 10:50 | 10 |
But why every 30 seconds ?? To stop it he has to turn off/on
the DECconcentrator...
Could it be a FW bug ??
Thank's for your replies !
Thierry A.
| |||||
| 914.5 | Ring down / Ring up - Initializations | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Fri Apr 23 1993 11:56 | 12 |
One of my customers is having the same problem. Configuration is
simple. DECconcentrator 500 with 1 VAX and 2 SUNs all connected via
SAS.
These ring inits occur in spurts. The ring down/up occurs in less than
a second. Sometimes we can get two ring down/up toggles in 1 second.
What counters are best to look at to point us to the problem, besides
the counters mentioned?
Thanks,
Dan
| |||||