| 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 |
I have a customer who is using SLIP to access the hub. He is able
to ping the hub. However he gets an error msg "SYSTEM ERROR" when
he tries to bring up the hub front panel. He is using version 4.1.1
of hubwatch and the Hub is at 4.0.1. This was working fine before
he upgraded to Hubwatch 4.1.1. Although his HW version was 3.1.
Any ideas?
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3315.1 | the computer not the network | MXOC00::CSILVA | Wed Feb 28 1996 10:45 | 10 | |
Typically a "system error" message refers to a problem
with the system running Hubwatch, instead of a network
related problem ("no response from agent").
V4.0 consumes more memory, do you have at least 8 Mb of RAM,
and a swap file of 20Mb?.
Check the readme file for other known problems.
| |||||
| 3315.2 | NETCAD::MILLBRANDT | answer mam | Wed Feb 28 1996 11:09 | 1 | |
Also your hub should be at 4.1.0 (or 4.1.1) with Hubwatch 4.1. | |||||
| 3315.3 | reloading hubwatch fixed problem | JULIET::WENGER_GE | Thu Feb 29 1996 19:10 | 1 | |
reloading hubwatch fixed problem | |||||
| 3315.4 | Exit and reenter fixes stuff sometimes | PTOJJD::DANZAK | Pittsburgher � | Sun Mar 03 1996 07:41 | 9 |
With hubwatch, in general, after doing complex operations you can loose
contact with the hub - i.e. "no response from agent" etc. I've found
that typically you need to exit HUBWATCh and restart it. In just about
all of these cases I've found that exiting windows and/or rebooting and
rerunning will fix it. Stuff that is complex = portswitch32 management
etc., seems to kill it.
PCs are truely wonderful,
j
| |||||