| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
Hello,
A customer has 24 DEChub 900s; four are set up as shown below. The first
WR90 in the first hub is doing IP. The second WR90 in the first hub is
doing IP and IPX. The WR90 in the third hub also is doing IP and IPX.
All is well until...
...the customer adds a second WR90 in the third hub; this
WR90 is set up to route IP and IPX. As soon as the WR90 is added, the
customer get NETBIOS floods from two NT workstations on the 900TM of the
4th hub. This takes the entire network down, across all 4 hubs. The
WANrouters do NOT forward NETBIOS.
It appears that this is not a hardware problem, as the DEChub modules have
been swapped from hub to hub with no change in symptoms.
Anything obvious he is missing?
Thanks in advance for any insight,
Craig Pahigian
+-----------------------+
+------------------+ | |
+-|---------------+ | +-|---------------+ +-|---------------+
| | | | | | | | | |
| 9 W W | | | 9 | | 9 W |
| 0 R R | +----0 | | 0 R |
| 0 9 9 | | 0 | | 0 9 |
| 0 0 | | | | 0 |
| E | +----M | | E |
| F | | | X | | F |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
+-----------------+ | +-----------------+ +-----------------+
HUB #1 | HUB #2 HUB #3
|
|
+------------------+
|
+-|---------------+
| | |
| 9 9 |
| 0 0--------------------\
| 0 0 | \ NT
| | / WORKSTATIONS
| E T--------------------/
| F M |
| |
| |
| |
| |
| |
| |
| |
+-----------------+
HUB #4
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3494.1 | ipx helper-address may be the culprit | PASAGE::PLUNKETT | Fri May 10 1996 18:55 | 8 | |
An NT system will try to use Netbios over native, ip, and ipx
transports, by default. If you have an IPX helper address defined
on the WANrouter, the router rebroadcasts these ipx requests. Each
ipx helper-addressed router on the lan will rebroadcast each
system's requests. There's your flood. Look for IPX broadcasts for
socket 04-55.
-Craig
| |||||
| 3494.2 | How is the helper address defined? | FOUNDR::CRAIG | Mon May 20 1996 13:28 | 10 | |
Hi Craig,
I was looking in the WANrouter90 owner's manual but saw no reference to
how to set the address. On page 3.20 there's a reference to a
"WANrouter 90/150/250 Installation Guide" but I couldn't find this
document in NAC::'LENAC_USER:[NETWORKS.HUB...]'
Thanks again for the assistance,
The "Other" Craig
| |||||
| 3494.3 | Is the WANrouter 90 a Disco box? | PASAGE::PLUNKETT | Thu May 23 1996 15:08 | 10 | |
I only know how to do it for a DECbrouter/Cisco box. You go into
config for a particular interface, and issue the comand "no ipx
helper-address" That turns off the IPX rebroadcasting.
To define it, you go into the interface config and type ipx
helper-address <novell net number of interface>.FFFF.FFFF.FFFF<cr>
The F's tell the router to do be a helper for all systems on the
wire.
-Craig
| |||||
| 3494.4 | Final update | FOUNDR::CRAIG | Wed Aug 21 1996 23:25 | 12 | |
Just an update; the customer has not been able to solve this problem,
either due to his inability (even with DEC's help) to uncover some
arcane command string, or due to a bug in hub functionality. I expect,
therefore, that the customer will move away from DEC hubs since their
presence in the network is preventing him from attaining the
connectivity he needs for his business.
Thanks for the help, by the way. Much appreciated, notwithstanding the
outcome.
P.S. We have ten Hub 900s in our shop in Salem and have had oustanding
results with them. No IPX/SPX, however.
| |||||
| 3494.5 | Was this customers problem properly escalated? | NETCAD::BATTERSBY | Tue Sep 03 1996 16:24 | 9 | |
I'm curious as to what level of escalation "(even with DEC's help)"
this was taken to.
Also was it considered posting the base note in the common_brouters
notes conference, to make sure there might not be some solution
that could be discussed not possibly previously considered?
I'd hate to see a customer get turned off and go to the competition
because of lack of escalation of this through proper channels.
Bob
| |||||
| 3494.6 | could this be the problem? | CSC32::D_PERRIN | Mon Sep 09 1996 21:35 | 41 | |
=============================================================================
Copyright Microsoft Corporation 1995.
Browser Service Causes Network Broadcast Storm After 1193 hrs
PRODUCT NAME: Microsoft Windows NT
SOURCE: Microsoft Corporation
MSKB Article: Q136935
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft Windows NT Server version 3.51
----------------------------------------------------------------------
SYMPTOMS
========
Windows NT Server 3.51 starts a broadcast storm on the network with browser
frames after the Windows NT Server has reached the System Up Time of 1193
hours, which means it has been running continuously for 1193 hours or
multiples thereof. These broadcast frames are sent out on all installed
protocols. The broadcast storm typically last less than 5 or 6 minutes and
then stops by itself. The broadcast browser frame types that appear are the
"Host Announcements" or the "Local Master Announcements" frames, which are
typically sent out every 12 minutes.
STATUS
======
Microsoft has confirmed this to be a problem in Windows NT version 3.51.
This problem has been corrected in the latest U.S. Service Pack for Windows
NT version 3.51. For information on obtaining the Service Pack, query on
the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Solution: Upgrade to Windows NT 3.51 Service Pack 2 or later.
| |||||