| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3079.1 | Solution. | CGOS01::DMARLOWE | Have you been HUBbed lately? | Mon Dec 18 1995 11:36 | 5 |
| Unless the 90TL has 4 MB of memory, it will disappear or not work when
polled by HUBWATCH. When you ADD the 90TL to the slot, you must
DISABLE POLLING. After that clicking on the module will work.
dave
|
| 3079.2 | To poll or not to poll... | LEMAN::PAIVA | Hawkeye - Network Support @GEO | Tue Dec 19 1995 03:33 | 18 |
| Dave,
>Unless the 90TL has 4 MB of memory, it will disappear or not work when
>polled by HUBWATCH. When you ADD the 90TL to the slot, you must
>DISABLE POLLING. After that clicking on the module will work.
Oh, I didn't know this 1MB/4MB difference. You mean that when HUBwatch
restarts, the polling "will make it not work" as would enable polling
while in the same "HUBwatch session" do?
What I asked on the fly, was the meaning of the DISABLE STATUS POLLING
box in the Configuration-Add window; is this a capability of disabling
polling for the particular module being added when "General" polling is
enabled?
Cheers,
Pedro
|
| 3079.3 | DISABLE is good. | CGOS01::DMARLOWE | Have you been HUBbed lately? | Tue Dec 19 1995 11:33 | 17 |
| >>You mean that when HUBwatch
>>restarts, the polling "will make it not work" as would enable polling
If you have a 1 MB 90TL and polling is enabled, the module disappears
when HUBWATCH polls all the slots in the hub. This is because the 1 MB
version does not have enuf memory for the code to respond to polls. As
the module cannot/does not respond, HUBWATCH deletes it. After all,
why would you reserve a slot when "nothing" is there?
>>is this a capability of disabling
>>polling for the particular module being added when "General" polling is
>>enabled?
Yes.
dave
|
| 3079.4 | slight refinement. | SLINK::HOOD | My God, what have I done to my spleen? | Tue Jan 02 1996 16:11 | 24 |
| > If you have a 1 MB 90TL and polling is enabled, the module disappears
> when HUBWATCH polls all the slots in the hub. This is because the 1 MB
> version does not have enuf memory for the code to respond to polls. As
> the module cannot/does not respond, HUBWATCH deletes it. After all,
> why would you reserve a slot when "nothing" is there?
'tain't HUBwatch that does the polling with the "slot polling" pushbutton.
This is the hub's agent's polling enable/disable.
When you add a module and set it to no slot polling, the slot table in the hub
has the module in it permanently. So, when an SNMP request comes from anywhere
to ask what's in the hub, that module will show up.
If you set the module to slot polling enabled, the hub manager will maintain
a dynamic slot table entry. In other words, the hub manager will ask the
slot every few seconds "who are you".
Older 1 meg non-NAS 90TL's do not respond to hub manager polls once they
start running terminal server software. So, it is important to disable slot
polling for the older 90TL's.
Newer 90TL's and 90M's are autodiscovered and don't need all this malarky.
Tom Hood
|
| 3079.5 | refinement of the refinement | NPSS::JOHNSON | Mike J., Network Products Support | Tue Jan 02 1996 16:23 | 15 |
| re: .4,
The implication that there is an "old" non-DNAS and a new "DNAS" version of the 90TL
may make people start checking hardware revs. Don't. The DSRVE product is the only
DS90TL product that we sell and it has but 1 MB of memory - hence "non-DNAS". There
once was a DSRVE-UG and a DSRVL that were "return to factory" 4 MB upgrades but both
of these were retired about two years ago. The replacement was an "install it yourself"
4 MB upgrade kit called DSRVE-SK. However, due to material shortages, this product
has been unavailable for several months.
The bottom line is that this is NOT an old versus new problem. Rather, it is one
of memory size and ALL STOCK DSRVE's have 1 MB. SOME may have been upgraded to 4 MB
but that is the exception, not the rule.
/mj
|