| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1384.1 | Sorry, not in HUBwatch v3. | SLINK::HOOD | I'd rather be at the Penobscot | Wed Sep 07 1994 11:38 | 12 |
| > Each time a DECHUB is entered in a HUBwatch session the default
> setup is POLLING OFF. Is there a way of configuring HUBwatch
> for POLLING ON in startup.
We thought about doing that a while ago, but it never got beyond the
"thought-about" stage. So, you cannot do it in HUBwatch V3.x. It's a pretty
simple thing to add (we did put the hooks in for it), so maybe it can get in
version 4 this winter.
Sorry,
Tom Hood
HUBwatch
|
| 1384.2 | Perhaps as a Startup Option Window? | MSDOA::REED | John Reed @CBO, DTN:367-6463, KB4FFE, SouthEast | Wed Sep 07 1994 21:50 | 9 |
| Please, if you are going to enable auto-polling, PLEASE give the poller
the intelligence to keep old hand-forced modules (such as DS90L, 90L+
servers) on the backplane.
I have not encouraged my customers to use polling on the Hubs that
contain older modules, and I would HATE to have HUBwatch come up
polling by default, and EAT UP the module assignments each time.
JR
|
| 1384.3 | polling vs polling | SLINK::HOOD | I'd rather be at the Penobscot | Thu Sep 08 1994 11:22 | 13 |
| John,
I think you're confusing the polling the DENMA does (to see what's in its
slots) with the polling HUBwatch does. They are two completely different
operations. HUBwatch polling will *not* kick modules out of a hub which
have been manually put there. DENMA slot polling (if enabled) will do this
because the modules you mentioned don't reply to DENMA polling.
So, it is *always* ok to enable HUBwatch polling. It does not cause the
DENMA to slot-poll. Rather, it just gets the DENMA's existing slot info.
Tom Hood
HUBwatch
|
| 1384.4 | Which Screen controls DENMA Polling ? | MSDOA::REED | John Reed @CBO, DTN:367-6463, KB4FFE, SouthEast | Thu Sep 08 1994 12:23 | 27 |
| Tom,
This is good news for me. I am glad that the HUBwatch poller
is different from the DENMA poller. But now I am confused.
I don't understand how to disable DENMA polling. When I
hand-insert the older modules, and type in a MAC address, these
modules show up, and they don't dissappear. When I exit HUBwatch
and return again, the older modules still appear.
What tells the DENMA to poll it's slots? Or when would the DENMA
poll it's slots. Can I have DS90L, and DS90L+ modules in a hub90
along with DR90T, and DR90C and DECbridge90FL modules and receive
a TRAP when I pull out a Repeater card. Does DENMA polling with
the new version V2.1.3 (DENMA021.SYS) support detecting new module
insertion and removal while allowing me to keep the definition of
older modules in other slots?
What button do I press to insure that DENMA polling is in the proper
state to keep my customer from having to re-enter his terminal server
modules, but still receive alarms and traps when something scary occurs?
Thanks,
JR
|
| 1384.5 | "Enable Status Polling" | SLINK::HOOD | I'd rather be at the Penobscot | Thu Sep 08 1994 13:36 | 17 |
| One of the DENMA people will have to answer the DENMA-specific questions,
but...
> What button do I press to insure that DENMA polling is in the proper
> state to keep my customer from having to re-enter his terminal server
> modules, but still receive alarms and traps when something scary occurs?
In the HUBwatch Configuration->Add window, (where you add things like
the DB90 and DS90L), is a radio button labeled "Enable Status Polling".
This is what tells the DENMA to do its slot polling. By default, the
button is set (green). If you press it so it's off, you're telling the
DENMA, "Hey, I know darned well what I've got in this slot, so buzz off
and don't go contradicting me, you stupid computer you." [Well that's kind
of a paraphrase of what you're telling the DENMA, but you get the idea.]
Tom Hood
HUBwatch
|
| 1384.6 | Understanding DENMA polling | ROGER::GAUDET | Because the Earth is 2/3 water | Thu Sep 08 1994 16:10 | 30 |
| John...
The behavior you have seen is exactly correct. Manually adding (via
HUBwatch) the older modules like the DS90L and DS90L+ will retain those modules
in their respective slots. These modules do not respond to the DENMA's slot
polling, but the DENMA is smart enough to know that an "undiscoverable module"
has been added to that slot, so it will not mark it as empty just because there
is no response. The 1-Meg DS90TL was another story. This module would respond
to the DENMA's slot polling during the period when it was loading the software
image over the network (i.e. while it was running out of ROM). Once the
software was loaded, it would stop responding to the DENMA's slot polling. The
effect of this was to have a 90TL which would appear in the hub for a short
time, then suddenly disappear. The solution was to add the module via HUBwatch
with status polling disabled. This would allow the module to be retained in the
hub view regardless of which code it was running (ROM or software).
If, for some reason, you want to disable the DENMA from all status polling,
you can do so via the DENMA's console setup port. Select option [9] from the
menu and you can disable backplane management. Note that this will disable
polling of all slots in the hub as well as the polling of remote hubs through a
DECbridge 90/90FL. You cannot disable the DENMA's backplane management from
HUBwatch.
Regarding traps, yes the DENMA does issue several enterprise-specific traps
which indicate things like module insert(add)/remove(delete), port status
change, and module status change (this one is useful for the DS90L/L+ modules
when they become "unreachable" for one reason or another). See that last couple
of pages of the DECHUB90 MIB for details about the traps generated by the DENMA.
...Roger...
|