| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2064.1 | | NPSS::RAUHALA | | Thu Jun 13 1996 16:04 | 17 |
| It seems that the 620 is unable to respond to it's own address.
Rather than processing the management packet (addressed directly
to the bridge) it instead treats it like a regular packet and will
forward/filter it.
The reason the arp request works is that it gets send to the
broadcast address, not a specific device address.
was the customer seeing any crashes before installing V1.4 code?
Is it possible to check (using snmp or MCC) the status of the
4 addresses of the bridge while it's in this messed up state?
Normally an address will be "learned" on port 1-4 but the
4 bridge addresses should never be learned on any port, their
status should be listed as "self". I'm thinking maybe the
status got messed up somehow.
ken
|
| 2064.2 | Static entries with problems... | 54625::VANLOOCK | Patrick DTN 856-8648 | Fri Jun 14 1996 05:38 | 39 |
|
Ken,
According to some notes I made at that time:
(hand written, no logfiles, so I'm not quite shure about query/answer)
queries done after 'moving' MCC-station to first Ethernet-port (Line 2)
of this bridge ...
MCC> dir bridge jnj_ns:.janbel.bridges.decbridge_620_binfb2
Address = { 08-00-2B-2C-76-FB, <== FDDI-port
08-00-2B-6C-76-FB,
08-00-2B-2C-76-FC,
08-00-2B-6C-76-FC }
MCC> show bridge jnj_ns:.janbel.bridges.decbridge_620_binfb2
forwarding database static entry 08-00-2B-2C-76-FB all char
==> reply: 'variant selector information not found in
variant selector list'
MCC> show bridge jnj_ns:.janbel.bridges.decbridge_620_binfb2
forwarding database static entry 08-00-2B-6C-76-FC all status
==> reply: no such entity
At this moment: all bridges behave well, so I can't get more
(accurate) info...
V1.4 was installed more than 1 year ago: reason: monitoring
via SNMP...
What do you mean with a 'crash'? Customer didn't complain about
lost connections ...
Patrick
|
| 2064.3 | | NPSS::RAUHALA | | Fri Jun 14 1996 18:01 | 11 |
| by "crash" I mean an Unsolicited Reset.
the bridge will be down for about 1 minute while
it runs diags and pre-forwarding mode. I was
wondering if they had any history of crashes
with old V1.3 code.
Is this customer problem fairly recent (1-3 months)
or have they been seeing this problem since they
started using V1.4? (over 1 year).
ken
|
| 2064.4 | no "crash" seen last months... | 54625::VANLOOCK | Patrick DTN 856-8648 | Mon Jun 24 1996 11:14 | 17 |
|
Hi Ken,
Sorry for this late reply (I've been 'out' for a week...)
The customer can't remember when this problem first occured but
he guess about six months ago.
Although the "Unsolicited Reset" counter on the bridges that recently
experienced management-problems is now at 3 on bridge BINFB2 and
1 on bridge BINFB6, customer was not aware of any 'unexplainable reset'
as a "crash" would have caused.
Checking the unsolicited resets on the other bridges: bridge BINFB4
has currently 1, the other 2 (BINFB3 and BINFB5) have 0.
Patrick
|
| 2064.5 | | NPSS::RAUHALA | | Mon Jun 24 1996 15:55 | 3 |
| we are working on trying to duplicate the problem...
ken
|