[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
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 |
1770.0. "HUBwatch hangs on notebook with PCMCIA adapter" by DECPRG::PAVLUP () Fri Dec 09 1994 03:43
I ran into some troubles when doing a configuration of hub 900 at
customer site from my HUBwatch configuration on notebook.
The configuration was: HUBwatch V3.1 on DECpc 325SL with PCMCIA network
adapter, and a hub 900 with firmware V3.1.
When opening HUBwatch with the hub manager agent specified, HUBwatch
started working, exchanging data with the hub manager, even the initial
data-entry window became grey (which is normally followed by displaying
the hub view after some time), but then in this state HUBwatch hangs
(no activity visible, even no activity on the network adapter). I let it
"do" this nothing for about 10 minutes, but it seems to be forever...
When opening HUBwatch with a single-module agent (e.g. bridge 900MX - SW1.4),
it worked normally, and the module view came quite quickly.
For me it looks as if some timers were too short (even the PCMCIA adapter
is not the fastest thing) or something like that. Unfortunately, I did not
have chance to experiment on site (I was also installing HUBwatch on a
customer's PC - V3.1 - and it worked just fine). I'm not able to restore the
situation in office, as I don't have hub here, and on single modules it
works fine.
As need to have working HUBwatch on my notebook (when going to customers),
I'd appreciate any hint, help and information that would help me get
HUBwatch normally working.
Thanks for any answer.
Petr.
T.R | Title | User | Personal Name | Date | Lines |
---|
1770.1 | E-Nuf Memory? | POBOX::ELARSON | | Fri Dec 09 1994 12:10 | 9 |
| Petr,
A problem I ran into that sounds familiar... Hubwatch took 1.5 hours to
paint the picture of the hub with 7 modules. It worked fine with up to
4 modules, but after that you might as well go to lunch. As it was,
the problem was not enough memory in the PC. I was also using a DEPCA
instead of a PCMCIA adapter.
Ed
|
1770.2 | 8 Megs too low...? | DECPRG::PAVLUP | | Mon Dec 12 1994 03:04 | 10 |
| Hi Ed,
I've got 8Meg notebook that I'm using to run the HUBwatch. It should be in line
with SPD. Do you think that 8 Meg might be too low...?
Anyway, thanks for the response - at least I know now that it's nothing
special about my installation...
Regards Petr.
|
1770.3 | Works nicely for me. | MSDOA::REED | John Reed @CBO, DTN:367-6463, KB4FFE, SouthEast | Mon Dec 12 1994 11:05 | 9 |
| Nothing Special. I have been running HUBWatch for windows on my DCWB
laptop (425sl, 8 meg, PCMCIA Xircom) and it works nicely. I can't run
NDU, but I can run Probewatch. I use the Pathworks v5 TCP/DECnet
stack.
I have not been able to get the DECROU software to load using my v5.0
stack yet, but I'm attempting to do that too.
JR
|
1770.4 | OK with more memory.... | SCCAT::MILLER | | Wed Jan 04 1995 17:03 | 5 |
| I had the same problem on my 425SE with 8MB of memory - it would work
(slowly) for up to 4 modules in a DEChub 900. Any more would cause it
to hang. The solution?? 20 MB of memory. Works great now up through
a full hub. BTW, I'm also using a PCMCIA adaptor, and NDU works fine
(with the Windows for Workgroups IP stack).
|