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 the following problem: Hubwatch for VMS 3.0, decserver 90tl, connected on hub900, this decservers are with 1.0 mb of memory , software version 1.1a. We want to manage this decservers from a privileged community in order to read/write (privil) and from the another community in order to read only(public). All this we need using the hub representation from hubwatch. We define on the servers 90tl the following: SNMP State: ENABLED Authentication Failure: ENABLED Community Name Address GET GETNEXT SET TRAP PUBLIC 7.0.0.1 ENA ENA DIS DIS PRIVIL 7.0.0.1 ENA ENA ENA ENA After: We make: 1. Configure the hubs and all the modules with community name privil and with the public. 2. All the modules 90tl was added with the option ADD from the hubwatch using the community name privil. After the access using this community name is good , inclusive after exit hubwatch and return to hubwatch. 3. After we added the decserver 90tl with the option ADD from the hubwatch using the community name public. In this case hubwatch give us the following message: "failed to update slot information into the hub", but inclusive after this error it's possible the access to the module until exit of Hubwatch. 4.After 3. When we reconnect to Hubwatch and to try to access to the module with the community name privil the message is "No agent specified for the slot mac address" Please, some people understand the problem and says to us that we make bad, and what are the exact steps in order to manipulate the servers with the two communities from hubwatch using of the representation of the hub. Thanks in advance, Elsa Soengas MCS Spain
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1652.1 | agents file? | SLINK::HOOD | I'd rather be at the Penobscot | Thu Nov 03 1994 10:25 | 4 |
Don't forget to add the DECserver 90TL into your hubwatch agents file. Tom Hood HUBwatch | |||||
1652.2 | yes, one question??? | ISIDRO::ELSA | Thu Nov 03 1994 10:35 | 11 | |
Hi, The dec servers 90tl are in agent file, but I have a question, I should have two entries or one for each decserver???. If the answer is two entries how is each entry??? Thanks in advance, Elsa Soengas P. | |||||
1652.3 | Good question. | SLINK::HOOD | I'd rather be at the Penobscot | Thu Nov 03 1994 10:44 | 17 |
Two entries. Give them two different agent names, as well. Enter the read-only one first. But, what I would suggest is the following: - Put the DECserver90TL's read-only agent in the agents file. This will be used by HUBwatch when you manage the 90TL through the hub. Using it this way will give you read-only access to the TL. - Put a 2nd entry for the 90TL in the agents file, with a *different* agent name, and with the read-write community. Then, to do the read-write operations, manage the 90TL directly (ie: double-click on the 2nd entry in the Community->Manage Table window). Tom Hood HUBwatch | |||||
1652.4 | thanks | ISIDRO::ELSA | Thu Nov 03 1994 10:53 | 10 | |
Thanks, Tomorrow I will prove on the customer site, and I will put here the results. Elsa Soengas MCS Spain | |||||
1652.5 | Tested and Approved ... | PRSSOS::PEYRACHE | Jean-Yves Peyrache Country Support Group France | Thu Nov 03 1994 12:50 | 8 |
No problem, follow informations keep in Configuration and installation manual for Hubwatch and Tom's step works perfectly. Just don't forget to disable the status polling for All 90TL stuff Jean-Yves |