| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 112.1 | Try the current version of bridge code | EMDS::SEAVER | LENAC Net Mgnt Mktg 223-4573 | Tue Dec 29 1992 01:25 | 9 |
| try loading the current version of the bridge code onto your bridge.
It is V3.0. V1.14 is not guaranteed to manage anything!
As of 28 December 1992, the following files are on the public directory
EMDS::MANAGEMENT: To copy a file from this directory, type:
COPY EMDS::MANAGEMENT: file_name
where file_name is the name of the file you want to copy.
# BRIDGE_LOAD.TXT= How to load new micro-code on bridge
|
| 112.2 | I'll give it a try.. | MORO::MAUTZ_RI | Networks >= to DECnet | Tue Dec 29 1992 14:00 | 4 |
| Thanks for the quick reply. I'll get that done ASAP and post the
result here!
Richard
|
| 112.3 | Problem is still there! | MORO::MAUTZ_RI | Networks >= to DECnet | Thu Dec 31 1992 17:14 | 126 |
| 112.4 | Same problem for PC addresses | LEMAN::BRUNNER | | Tue Jan 05 1993 10:39 | 26 |
| Hi Gurus,
What I posted a while ago:
<<< NAC::DISK$WORK295:[NOTESLIBRARY_1]RBMS_LANBRIDGE100.NOTE;1 >>>
-< RBMS and LAN Bridge 100 Notes >-
================================================================================
Note 567.0 Addresses moving between ports on DECMR ? No replies
LEMAN::BRUNNER 20 lines 21-AUG-1992 04:46
--------------------------------------------------------------------------------
Customer reports a problem with DEWGB90's when trying to locate
addresses on a DECMR90 port. Addresses seem to move once in
a while to another port, no need to say that the PC or system hasn't
moved in the meantime. If the PC is moved to another DEChub 90 its
address moves in the 15 minutes (450*2 second aging out), this is
correct. They are using "ccr" on an Ultrix station.
Customer has about 1000 PC's connected with 12 VAXservers (3100's and
4000's). Customer's tool available on SOLARX:: (node 48.522) as saveset.
DECbridge 90 V1.14 firmware 1.4
Tried V2.5b, V2.9 and V3.0 on one DECbridge, same results.
All DEWGB are at version 3.0 since Christmas and they all exhibit the
same errors. Is this a known problem ?
Compressed tar file available on SOLARX:: as "itu.tar.Z"
Thanks for looking at it.
Walter
|
| 112.5 | Logged a CLD! | MORO::MAUTZ_RI | Networks >= to DECnet | Mon Mar 15 1993 22:37 | 8 |
| I mailed 112.* to engineering and they have been unable to make time
to look into this problem. Today I logged a CLD through the product
support organization to see if something can't be done.
I'm curious to know if anyone using HubWatch (any flavor) has verified
the accuracy the configuration information.
Richard
|
| 112.6 | I think I know part of what went wrong here | PRNSYS::LOMICKAJ | Jeffrey A. Lomicka | Tue Apr 06 1993 19:59 | 56 |
| 112.7 | same problem...different site... | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Fri Apr 30 1993 13:50 | 8 |
| I have a customer who is reporting the same problem.
Show repeater will report multiple devices in the same slot, or
repeaters in empty slots.
I think they logged a call today, so I guess there will be another CLD
open on this soon as they are *real* unhappy about this.
I am going there monday, so will try the bridge address ageing stuff...
thanks,
Mike
|
| 112.8 | Minor Update! | MORO::MAUTZ_RI | Networks >= to DECnet | Fri Apr 30 1993 22:03 | 14 |
| Jeff, I tried your .6 suggestion but the problem only seemed to be
worse. I then realized that with the infinite age out, none of the
bogus entries would ever age out either (I guess). I have now
gone through the following process:
1. Set age to 2 seconds - wait a few seconds
2. SET and DEFINE age to 43200 (21600*2).
I'll have a look at this in a few days - end of next week as I'll
be out of town the first three days of the week!
Regards,
Richard
|
| 112.9 | We also see strange address reports | BSS::AMBER | Mark Amber, CXO3 LAN Mgr. (DTN)592-4645 | Fri Apr 30 1993 22:07 | 30 |
| I have a similar situation, but the previous explaination does not fit this
senario. With a 16-slot hub, and one DEWGF (v3.1) in slot 8. Whenever we
do a SHOW ADDRESS, and then wait a bit and do it again, the report appears
to show addresses moving from one hub to the other. What we see is that
the slot and port numbers are unchanged, but they flip back and forth between
hub1 and hub2. The nodes themselves are not moving, just the way the bridge
reports it. Check out the following SHOW ADDRESS outputs, both given within
a few seconds of each other (only the first 5 addresses are included, but
the symptom appears throughout the list. Note that not every address does it.
DECbridge> SHOW ADDR
Address 1: AA-00-04-00-AC-72 hub 1 slot 5 port 5 !ADDRESS 1 IN HUB 1
Address 2: AA-00-04-00-BB-72 hub 1 slot 1 port 1 !ADDRESS 2 IN HUB 1
Address 3: AA-00-04-00-60-F8 hub 2 slot 2 port 2
Address 4: AA-00-04-00-48-F8 hub 2 slot 6 port 1
Address 5: AA-00-04-00-4C-F8 hub 2 slot 7 port 6 !ADDRESS 5 IN HUB2
Address 6: AA-00-04-00-59-F8 hub 1 slot 1 port 1
.
.
.
DECbridge> SHOW ADDR
Address 1: AA-00-04-00-AC-72 hub 2 slot 5 port 5 !ADDRESS 1 IN HUB 2 !!!
Address 2: AA-00-04-00-BB-72 hub 2 slot 1 port 1 !ADDRESS 2 IN HUB 2 !!!
Address 3: AA-00-04-00-60-F8 hub 2 slot 2 port 2
Address 4: AA-00-04-00-48-F8 hub 2 slot 6 port 1
Address 5: AA-00-04-00-4C-F8 hub 1 slot 7 port 6 !ADDRESS 5 IN HUB 1 !!!
Address 6: AA-00-04-00-59-F8 hub 2 slot 1 port 1
.
.
.
|
| 112.10 | more of the same.. | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Mon May 03 1993 06:21 | 7 |
| re: .9
The site I was at has a 16 slot hub.
I am going there tomorrow and will some more details, but I think it
was similar to what you were seeing.
I have opened a CLD on this today....
thanks,
Mike
|
| 112.11 | hubwatch currently considered useless!! | GIDDAY::DRANSFIELD | Mike Dransfield, Sydney RSSG | Tue May 04 1993 07:04 | 11 |
| re: .10
I went to site and hubwatch is considered useless unless the address
information on the repeaters is correct.
They also would like the ability to restrict a repeater port to every
using one address so that they can stop people from randomly moving
their pc's around to different ports (as all the other vendors hubs do
was added as a comment...eg cabletron etc)
With 2 CLD's open is there any progress being made on this problem?
thanks,
Mike
|
| 112.12 | Not in DEChub 90 modules | CGOS01::DMARLOWE | dsk dsk dsk (tsk tsk tsk) | Tue May 04 1993 16:42 | 5 |
| You won't be able to lock addresses to keep people from moving with
the 90T and 90C repeaters. You will have to wait for the 900 modules.
Maybe the 8 port min modules will have that feature. I don't know.
dave
|
| 112.13 | Engineering is Working on This! | MORO::MAUTZ_RI | Networks >= to DECnet | Thu May 06 1993 01:43 | 7 |
| According to the latest status on my CLD (# CXO09906), engineering is
"actively working this issues". They expect to have resolution by the
end of May!
Regards,
Richard
|
| 112.14 | Age Timer Didn't Help! | MORO::MAUTZ_RI | Networks >= to DECnet | Fri May 07 1993 16:18 | 17 |
| Adjusting the bridge age timer doesn't seem to help a lot. I still
see multiple addresses showing up on the same hub/slot/port of the
90Ts. As an example, one of the ones I just looked at was
Address 1: AA-00-04-00-07-08 Hub 2 Slot 7 Port 1
.
.
.
Address 34: 08-00-2B-26-4D-64 Hub 2 Slot 7 Port 1
Address 1 is a node a DECnet address 2.7 and its Ethernet hardware
address is 08-00-2B-30-90-E1. I also know that the customer has
not moved this node (hub/port/slot wise) in a long time.
Regards,
Richard
|
| 112.15 | address securtiy coming | EMDS::SEAVER | Bill Seaver, HUBwatch Mktg | Thu Jun 03 1993 01:42 | 6 |
| I have asked the engineer about the status of the fix.
re: address security (notes .11, .12) It will be in the 32 port DEChub
900 repeater and will eventually (December) be in an 8 port UTP
repeater that will fit into the DEChub 90. Both repeaters will have
their own SNMP agent and will not need a DECagent 90 or a DECbridge 90.
|
| 112.16 | The Check Is In The Mail! | MORO::MAUTZ_RI | Networks >= to DECnet | Mon Jul 26 1993 18:46 | 9 |
| Just for everyones info., engineer says they are still working on
resolving this problem. Currently, I have no status as to what is
really happening! The CLD is still open, the product support manager
in our area periodically asked engineer for an update, engineer says
they are still working on it!
Regards,
Richard
|