| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 509.1 | Check the documentation for proc/sys params. | SLINK::HOOD | I'd rather be surfing | Sun Nov 21 1993 23:39 | 13 |
| Based on your hang, you've probably got either system or process
parameters set incorrectly. The installation guide and the release
notes describe the set up. Please check them.
The release notes also specify 24 Meg of memory (although it will run
more slowly on 16 Meg).
As far as the priority, HUBwatch runs at whatever priority is set for
the process, including the normal incrementing of priority which
OpenVMS does automatically.
Tom Hood
HUBwatch Development
|
| 509.2 | Some more information | ARRODS::GILLJ | John, DTN 847-5849 | Mon Nov 22 1993 07:44 | 22 |
| Thanks Tom for your response. I appreciate your points around process
parameters and accept that performance will be slightly degraded when
running with 16Mb.
However, I have sone more investigation and found the following.
If I install the DECagent 90 in my hub and install a DECbridge 90 in
the hub. Then using the RS232 port on the agent, select option 14 and
configure the DECbridge in the hub, followed by option 18 connect to
the bridge, then at the DECbridge prompt issue the command SET BRIDGE
HUB_MANAGEMENT ENABLE.
Following this sequence I re-invoke HUBwatch from my workstation and
everything works as planned. I.E. The only time my workstation can run
HUBwatch and manage the hub is when I have a DECbridge 90 installed.
This will cause us a major problem as not all of the DEChubs on-site
will have DECbridge 90 installed.
Is this the expected mode of operation or am I doing something wrong?
John
|
| 509.3 | | QUIVER::SLAWRENCE | | Mon Nov 22 1993 14:26 | 1 |
| A DECbridge90 is required in the hub to manage it.
|
| 509.4 | DEChub 90 AND DECagent required? | ARRODS::GILLJ | John, DTN 847-5849 | Mon Nov 22 1993 14:36 | 14 |
| Are you saying that I need both a DECagent 90 and a DECbridge 90
present in a DEChub 90 to manage it, my understanding was that the
DECagent 90 was sufficient. This is certainly not the information
that has been passed to my customer.
We have also just accepted delivery of a DEChub 900 and I have noticed
the same behaviour (as described in .2). Do we also need a DECbridge
90 and DECagent 90 here (if we are not using the "in-built" hub
manager).
Regards,
John
|
| 509.5 | | QUIVER::SLAWRENCE | | Mon Nov 22 1993 14:46 | 14 |
| You need both a DECbridge90 and a DECagent90 to manage a DEChub90, but
the DECagent90 does not need to be in the same hub. It is capable of
managing several hubs, but each of those needs a DECbridge90 (any
flavor).
The DECagent90 V2.0 firmware will be capable of managing the hub it is
in without a bridge in the same hub (but will still need a DECbridge in
any other hub it is to manage).
The DEChub 900 does not need either a DECbridge or a DECagent to be
managable, _but_ if you do not configure any IP address for the hub
manager it reverts to a backwards-compatibility mode in which it allows
a DECbridge90 to become the hub manager, so it would behave the same as
the DECbridge90s.
|
| 509.6 | DECagent90 v2.0 firmware schedule? | ARRODS::GILLJ | John, DTN 847-5849 | Mon Nov 22 1993 15:03 | 8 |
| Thanks for the quick answer.
What is the current schedule for the DECagent90 v2.0 firmware?
Regards,
John
|
| 509.7 | A New Year's gift (we hope) | ROGER::GAUDET | Because the Earth is 2/3 water | Mon Nov 22 1993 15:22 | 5 |
| Early Q3FY94 is the expected availability of DECagent 90 V2.0 firmware. With
any luck, it'll be sooner.
...Roger...
DECagent 90 devo
|
| 509.8 | FT? | ARRODS::GILLJ | John, DTN 847-5849 | Tue Nov 23 1993 07:08 | 4 |
| Any chance of getting a field test copy?
JG
|
| 509.9 | Decbridge required for 90l servers only? | KERNEL::WARDJO | | Tue Nov 23 1993 11:15 | 22 |
| Hello,
Can someone explain why a DECbridge 90 is required in the hub as well
as the agent if only DECserver 90l & 90l+ are installed. I have removed
the bridge from my hub and hubwatch starts ok and I seem to be able to
manage the DECserver 90L+ ok. I understood that this would work as the
agent and the server talk RCF, but the DECbridge is required for
repeaters as it talks Bridge protocol with the agent and another
protocol with the repeaters (is it the Left Hitchcock or some such).
If this is the case, why should hubwatch hang when John (re .0) starts
it up without a bridge?
Any help in correcting my misunderstanding would be much appreciated.
Regards,
Jon
|