| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1671.1 | Known repeater bug, no solution yet | NETCAD::PAGLIARO | Rich Pagliaro, Hub Products Group | Tue Nov 08 1994 22:55 | 17 |
| A few customer have noticed this problem in repeaters (see note 1459
for more details). It is a known bug in version 1.1 repeater firmware.
We are still investigating the cause of this problem but have not been
terribly successful due to the relative infrequent nature of the
problem. We are still working on it.
Other than seeing the reset counters incrementing, can you tell me what
sort of impact this is having on your customer? That is, are they
merely curious or are they so upset that they want to return the units.
Also can you tell me who your customer is?
I cannot comment on the DECbridge 900 crash.
Regards,
Rich
|
| 1671.2 | More Info | COMBAT::LUND | Niklas Lund | Wed Nov 09 1994 10:45 | 14 |
| Hi
The customer is ASTRA-DRACO in Sweden. The problem with the repeaters have very
little impact, the customer have not noticed it yet. I have seen the repeater
problem twice when connecting to the repeater via DECHUB900 (ver 3.1) redirect
function. The repeater seems to reboot at the time of the connection. Is this
problemcommon to all repeaters ?, in note 1459 its a 900TM.
The crashing bridge of course have a lot more impact on the customer LAN.
Please advice on the bridge crash.
Thanks
Niklas
|
| 1671.3 | We need some detail on FDDI LAN hanging off the bridge... | NETCAD::BATTERSBY | | Wed Nov 09 1994 13:09 | 13 |
| Niklas -
The DECbridge 900MX error log you have provided suggests that
this is some kind of error related to FDDI.
Could you please provide us with a configuration for the FDDI
LAN hanging off the FDDI ports of the bridge. Once I have an
idea of the configuration, we'll be able to run this one by
some of our FDDI/network guru's.
Information like how many nodes, types of nodes (Novell, Sun)
other hardware hanging off the ring that the bridge is attached
to (like concentrators, other vendors bridges etc.)
thanks
Bob
|
| 1671.4 | Only DECbridges on the ring... | COMBAT::LUND | Niklas Lund | Wed Nov 09 1994 16:15 | 12 |
| Hi,
The ring consists of five DECbridge900MX rev 1.4. Nothing else is on the ring.
Three of the bridges are located in 1 DEChub900, 1 is installed in ONEhub and
the last one is in a DEChub900. All hubs have the latest firmvare rev.
I checked the MIBII error counters on the FDDI ports and they have not logged
any errors except some "Unknown protocol errors"
Thanks for your help.
Niklas
|
| 1671.5 | ...And there is absolutely nothing else in FDDI config? hmmm | NETCAD::BATTERSBY | | Wed Nov 09 1994 16:22 | 7 |
| So let me make sure I have everything you have provided us so far
about the bridges straight. You have 5 DECbridge900MX's in a ring
and only one of them has crashed. There is nothing else on the
ring, and there is no other extended topology of FDDI beyond this
ring with the 5 900MX's.
Bob
|
| 1671.6 | Still don't have enough detail.... | NETCAD::BATTERSBY | | Wed Nov 09 1994 16:44 | 24 |
| Niklas -
You've told us where the bridges are located, but we need to know
- What other modules are in the HUB with the 3 bridges
- Are there any backplane connections in this HUB
- What are the Ethernet connections in this HUB
- What other modules are in the HUB with the single bridge
- Are there any backplane connections in this HUB
- What are the Ethernet connections in this HUB
- What are the connections to the bridge in the DEChub ONE
Which of the 5 bridges is the one that crashes?
Can this crash be re-created at will?
How long before the crash occurs does the bridge appear to
operate ok?
Have the error logs of the other bridges been checked to see
if any errors have occured?
The more information you provide, the better the chances of us
being able to ascertain what might be happening.
Bob
|
| 1671.7 | What possible event may have occured just before crash... | NETCAD::BATTERSBY | | Wed Nov 09 1994 16:49 | 10 |
| And one other thing. If the crash is repeatable, can you
determine what you (the customer) are doing just prior to the crash.
IE: For example, is there a particular node on some Ethernet segment
which is initiating communication with another node on another
segment, and shortly after this, the crash occurs?
Perhaps the customer can tell you the time of day when they perceive
that "something" happened and they couldn't do or talk between
certain workstations anymore.
Bob
|
| 1671.8 | More information comming. | COMBAT::LUND | Niklas Lund | Wed Nov 09 1994 17:10 | 11 |
| OK
Yes you are correct, nothing but the five bridges are on the ring.
I think one of the other bridges have crashed as well and the crashes are NOT
reproduceable.
I will get back to you with answers to all your questions as soon as i
have all the information. Thank you very much for your help.
Niklas
|
| 1671.9 | DECbridge 900 crash. | STKHLM::SEDERLIN | | Thu Nov 10 1994 09:03 | 75 |
|
Hi Bob,
My name is Boa and I'm working with this customer together
with Niklas.
I should try to answer some of your questions.
The bridge in the DEChub ONE, I think we can forget
just now for this problem, I installed this bridge for
a few days ago 07-nov-1994.
HUB_1
3 * DECbridge 900MX
1 * DECrepeater 900FP
1 * DECrepeater 90C
Bridge 1
Port 1 Incoming FDDI-ring and to backplane FDDI-ring.
Port 2 Transceiver cable to a thick-ethernet segment.
Port 3 Connected to backplane thinwire-segment and
DECrepeater 90C is connected to this segment.
Port 4 Connected to backplane flexible channel 1 and
DECrepeater 900FP port 1 and 2 is connected to
this segment.
Port 5 Connected to backplane flexible channel 2 and
DECrepeater 900FP port 3 and 4 is connected to
this segment.
Port 6 Connected to backplane flexible channel 3 and
DECrepeater 900FP port 5 and 6 is connected to
this segment.
Port 7 Connected to backplane flexible channel 4 and
DECrepeater 900FP port 7 and 8 is connected to
this segment.
Bridge 2
Port 1 Connected to backplane FDDI-ring.
Port 6-7 Is outgoing to systems.
Bridge 3
Port 1 Outgoing FDDI-ring and to backplane FDDI-ring.
port 6-7 Is outgoing to systems.
HUB_2
1 * DECbridge 900MX
1 * DECrepeater 900FP
3 * DECrepeater 900TM
1 * DECserver 900TM
Bridge 1
Port 1 Incoming and outgoing FDDI-ring.
Port 2 Connected to backplane flexible channel 1 and
DECrepeater 900FP port 1 and 2 is connected to
this segment.
Port 3 Connected to backplane thinwire-segment,
3 * DECrepeater 900TM and 1 * DECserver 900TM
is connected to this segment.
Port 4 Connected to backplane flexible channel 2 and
DECrepeater 900FP port 3 and 4 is connected to
this segment.
Port 5 Connected to backplane flexible channel 3 and
DECrepeater 900FP port 5 and 6 is connected to
this segment.
Port 6 Connected to backplane flexible channel 4 and
DECrepeater 900FP port 7 and 8 is connected to
this segment.
Port 7 Connected to backplane flexible channel 5 and
DECrepeater 900FP port 9 and 10 is connected to
this segment.
I should try to get out to the customer next week and
get the error log entry from the 3 bridges in the same Hub.
Thanks for your help.
Boa
|
| 1671.10 | More error log entry | STKHLM::SEDERLIN | | Wed Nov 16 1994 12:15 | 172 |
|
Hi Bob,
Here is the error log entry from the other 3 bridges,
regards
Boa
DECbridge 900MX - slot 8 HUB_1 Bridge_1
==============================================================================
DECbridge 900MX, 6-Ethernet/FDDI Bridge, HW=v0/1,RO=v0.2,SW=v1.4.0
SysUpTime : 16 days 06:01:02 9 resets
SNMP Read/Write Community : dnb301a1
SNMP Trap Addresses : 157.96.132.2
Status of Last Downline Upgrade : No Status
In-Band Interface Hardware Address : 08-00-2B-A4-87-80
In-Band Interface IP Address : 157.96.128.250
In-Band Interface Default Gateway Address : Not Configured
==============================================================================
Entry # = 1
Entry Status = 0 [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id = 10
Firmware Rev = 1.4
Reset Count = 8
Timestamp = 0 E 5D67
Write Count = 5
FRU Mask = 0
Test ID = DEAD
Error Data = SR=0000 PC=03025D6E Error Code=00002020 ProcCsr=776D
Registers = D0=00002304 D1=00000001 D2=00000001 D3=00000003
D4=00000000 D5=00000000 D6=00000000 D7=0000FFFF
A0=00006890 A1=0004A798 A2=0005882C A3=000435C0
A4=000435C0 A5=00074968 A6=0004A71C A7=0004A6D4
Dump another entry [Y]/N?
Entry # = 0
Entry Status = 0 [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id = 10
Firmware Rev = 1.4
Reset Count = 7
Timestamp = 0 2D B48C
Write Count = 5
FRU Mask = 0
Test ID = DEAD
Error Data = SR=0000 PC=03025D6E Error Code=00002020 ProcCsr=7D6D
Registers = D0=00002304 D1=00000001 D2=00000001 D3=00000002
D4=00000000 D5=00000000 D6=00000000 D7=0000FFFF
A0=00006C38 A1=0004A7A8 A2=0005882C A3=00044C80
A4=00044C80 A5=00074968 A6=0004A72C A7=0004A6E4
Dump another entry [Y]/N?
No more Error Log entries.
==============================================================================
DECbridge 900MX - slot 7 HUB_1 Bridge_2
==============================================================================
DECbridge 900MX, 6-Ethernet/FDDI Bridge, HW=v0/1,RO=v0.2,SW=v1.4.0
SysUpTime : 27 days 03:44:17 6 resets
SNMP Read/Write Community : dnb301a2
SNMP Trap Addresses : 157.96.132.2
Status of Last Downline Upgrade : No Status
In-Band Interface Hardware Address : 08-00-2B-A6-5B-A8
In-Band Interface IP Address : 157.96.128.249
In-Band Interface Default Gateway Address : Not Configured
==============================================================================
DUMP ERROR LOG
Current Reset Count: 6
==============================================================================
Entry # = 2
Entry Status = 0 [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id = 10
Firmware Rev = 1.4
Reset Count = 5
Timestamp = 0 3 E85F
Write Count = 7
FRU Mask = 0
Test ID = DEAD
Error Data = SR=0000 PC=03025D6E Error Code=00002020 ProcCsr=776D
Registers = D0=00002304 D1=00000001 D2=00000001 D3=00000007
D4=00000000 D5=00000000 D6=00000000 D7=0000FFFF
A0=000068E0 A1=0004A798 A2=0005882C A3=00041B40
A4=00045B70 A5=00074968 A6=0004A71C A7=0004A6D4
Dump another entry [Y]/N?Y
Entry # = 1
Entry Status = 0 [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id = 10
Firmware Rev = 1.4
Reset Count = 4
Timestamp = 0 29 CE08
Write Count = 7
FRU Mask = 0
Test ID = DEAD
Error Data = SR=0000 PC=03025D6E Error Code=00002020 ProcCsr=7F6D
Registers = D0=00002304 D1=00000001 D2=00000001 D3=00000000
D4=00000000 D5=00000000 D6=00000000 D7=0000FFFF
A0=000069C0 A1=0004A798 A2=0005882C A3=00048340
A4=00048340 A5=00074968 A6=0004A71C A7=0004A6D4
Dump another entry [Y]/N?y
Entry # = 0
Entry Status = 0 [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id = 2
Firmware Rev = 1.8
Reset Count = 1
Timestamp = 0 0 1
Write Count = 7
FRU Mask = 2
Test ID = B02
Error Data = SR=0001 PC=00000004 Error Code=00000003 ProcCsr=0000
0:00000001 1:00000004 2:00000003 3:00000000
4:00000000 5:00000000 6:00000000 7:00000000
Dump another entry [Y]/N?Y
No more Error Log entries.
==============================================================================
Enter selection : 3
DECbridge 900MX - slot 6 HUB_1 Bridge_3
==============================================================================
DECbridge 900MX, 6-Ethernet/FDDI Bridge, HW=v0/1,RO=v0.2,SW=v1.4.0
SysUpTime : 27 days 04:01:05 5 resets
SNMP Read/Write Community : dnb301a3
SNMP Trap Addresses : 157.96.132.2
Status of Last Downline Upgrade : No Status
In-Band Interface Hardware Address : 08-00-2B-A6-89-50
In-Band Interface IP Address : 157.96.128.248
In-Band Interface Default Gateway Address : Not Configured
==============================================================================
DUMP ERROR LOG
Current Reset Count: 5
==============================================================================
Entry # = 0
Entry Status = 0 [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id = 10
Firmware Rev = 1.4
Reset Count = 4
Timestamp = 0 2D B0FE
Write Count = 7
FRU Mask = 0
Test ID = DEAD
Error Data = SR=0000 PC=03025D6E Error Code=00002020 ProcCsr=7F6D
Registers = D0=00002304 D1=00000001 D2=00000001 D3=00000000
D4=00000000 D5=00000000 D6=00000000 D7=0000FFFF
A0=00006498 A1=0004A798 A2=0005882C A3=00038670
A4=00038670 A5=00074968 A6=0004A71C A7=0004A6D4
Dump another entry [Y]/N?y
No more Error Log entries.
|
| 1671.11 | Need more specific information.... | NETCAD::BATTERSBY | | Fri Nov 18 1994 13:11 | 24 |
| Ok, after reviewing the error logs, it's clear that we still
do not have enough specific information. Given also that the
problem is not re-produceable at will, this will be difficult
to pin down without more specific information.
The "Unknown Protocol error" referred to in reply .4 is a
curious piece of information. Is there a very large number of these
in this counter, or just a few?
What we need is some information on the other parts of the
customer's network configuration.
questions that come to mind are;
1. What node types (systems) are connected to ports 6-7 of
bridge 2, and likewise to ports 6-7 of bridge 3?
2. What predominant protocol types make up the network traffic?
3. Is the customer using any other network management tools other than
SNMP in their extended LAN?
4. There is no description in reply .9 as to what "systems" might
be connected to the DECrepeaters. This might be crucial information.
In a sense, the bridges would appear to be crashing because something
is "talking" to the bridges in a way they cannot understand.
Bob
|
| 1671.12 | Another crash.... | ANTIK::WESTERBERG | Stefan Westerberg DC SN&O Stockholm | Mon Dec 19 1994 11:26 | 51 |
| Another DECbridge900MX, same company different city, is crashing every few days.
The HUB is configured with one DECbridge900MX, DECrepeater900FP and two
DECrepeater90C. The FDDI ring consists of DECbridges500, DECconcentrators500
and DEC FDDIcontrollers.
pcomErrLogNumEntries.0 :
INTEGER: 4
pcomErrLogTable.pcomErrLogEntry.pcomErrLogIndex.1 : INTEGER: 1
pcomErrLogTable.pcomErrLogEntry.pcomErrLogIndex.2 : INTEGER: 2
pcomErrLogTable.pcomErrLogEntry.pcomErrLogIndex.3 : INTEGER: 3
pcomErrLogTable.pcomErrLogEntry.pcomErrLogIndex.4 : INTEGER: 4
pcomErrLogTable.pcomErrLogEntry.pcomErrLogTimeStamp.1 :
Timeticks: (2066520) 5:44:25.20
pcomErrLogTable.pcomErrLogEntry.pcomErrLogTimeStamp.2 :
Timeticks: (3119500) 8:39:55.00
pcomErrLogTable.pcomErrLogEntry.pcomErrLogTimeStamp.3 :
Timeticks: (691340) 1:55:13.40
pcomErrLogTable.pcomErrLogEntry.pcomErrLogTimeStamp.4 :
Timeticks: (2242750) 6:13:47.50
pcomErrLogTable.pcomErrLogEntry.pcomErrLogResetNumber.1 : INTEGER: 10
pcomErrLogTable.pcomErrLogEntry.pcomErrLogResetNumber.2 : INTEGER: 9
pcomErrLogTable.pcomErrLogEntry.pcomErrLogResetNumber.3 : INTEGER: 8
pcomErrLogTable.pcomErrLogEntry.pcomErrLogResetNumber.4 : INTEGER: 7
pcomErrLogTable.pcomErrLogEntry.pcomErrLogInfo.1 :
DISPLAY STRING- (ascii): SR=0000 PC=03025D6E Error Code=00002020 ProcCsr=7D6D
D0=00002304 D1=00000001 D2=00000001 D3=00000000
D4=00000000 D5=00000000 D6=00000004 D7=0000FFFF
A0=00007E20 A1=0004A798 A2=0005882C A3=0002C5A0
A4=0003CF70 A5=00074968 A6=0004A71C A7=0004A6D4
pcomErrLogTable.pcomErrLogEntry.pcomErrLogInfo.2 :
DISPLAY STRING- (ascii): SR=0000 PC=03025D6E Error Code=00002020 ProcCsr=756D
D0=00002304 D1=00000001 D2=00000001 D3=00000000
D4=00000000 D5=00000000 D6=00000007 D7=0000FFFF
A0=00005FA0 A1=0004A798 A2=0005882C A3=0003BCE0
A4=00040BE0 A5=00074968 A6=0004A71C A7=0004A6D4
pcomErrLogTable.pcomErrLogEntry.pcomErrLogInfo.3 :
DISPLAY STRING- (ascii): SR=0000 PC=03025D6E Error Code=00002020 ProcCsr=756D
D0=00002304 D1=00000001 D2=00000001 D3=00000000
D4=00000000 D5=00000000 D6=00000004 D7=0000FFFF
A0=00008718 A1=0004A798 A2=0005882C A3=00047600
A4=000441A0 A5=00074968 A6=0004A71C A7=0004A6D4
pcomErrLogTable.pcomErrLogEntry.pcomErrLogInfo.4 :
DISPLAY STRING- (ascii): SR=2000 PC=00074966 Error Code=0000200C ProcCsr=556D
D0=00000000 D1=0000007F D2=00000078 D3=00000018
D4=0004A8D0 D5=00000000 D6=00000007 D7=0000FFFF
A0=00000000 A1=0004A798 A2=0004A870 A3=00061880
A4=030020D8 A5=03020000 A6=0003EB60 A7=0004A888
|
| 1671.13 | | NETCAD::ANIL | | Mon Dec 19 1994 16:20 | 9 |
| There have been very few (about 4) occurences of this particular
problem in the last several months. However, it is unreproducible
by us. We have produced an image that may help us track it down -- it
differs from the current released v1.4.0 only in that
when the box crashes, it logs different information that may reveal
the source of the problem. I'll communicate with you offline to
get you this image.
Anil
|