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 |
Hello, I am trying to manage a DECagent90 and a DECbridge90 standalone. I have hubwatch V4.1.1 Windows 3.11 on a DEC PC running Pathworks 5.1 . To make things easy I put the db90 SW3.9 and the DECagent90 V3.01 under my table and connected them via thinwire to my PC. I setup the DECagent90 from the console with IP address, GWY, Netmask, R/W Community. I start Hubwatch and enter the IP address of my DECagent90 and the R/W community string. As a result I get a blue map with a single DECagent90 Module displayed. This DECagent90 is fully manageable from here. Now according to the manual "Installation and Configuration" Table 3-7 DECagent90 Requirements under "Standalone" I added an entry for this DECagent90 in the Agent List Box. In the same Manual on Page 3-19 Table 3-8 DECbridges 90 an 90FL Requirements under "Standalone Requirements prior to adding module" I need a configured DECagent90 on the same LAN segment. (Section 3.5) and an Entry in the Agent List Box (Section 3.7). I think I fullfil these requirements. Under "Requirements for adding a module" Create a DECagent 90 Standalone community for the bridge. I select Community->Manage Table from here I open the "add" from Communities of Current Agent, and chose to enter a Standalone Community with a different r/o and r/w string than I already have for my DECagent90. After clicking on "ok" I see under an Index 2 my newly created community. On the same Window I make a new Entry in the Agent file where I specify: IP Address :of the DECagent90 Agent Name : of the " " Community :of the before created Standalone community Retry and Timeout I take the default MAC Address :here I enter the MAC address of the bridge Agent Type : I choose DECagent90 If I now select form the "Communities of current agent" the standalone community under Index 2 I get a blue screen with no modules on it. I can not configure anything with "Configuration->Add" because this is grayed out. When I select the new created entry from the agent file (the one with the IP address of the DECagent90 but with the MAC address of the bridge) I get an alert Box Hubwatch error MIB data not available (NoSuch) When I add a community to the agent and configure a hub90 and make this community current I get an empty HUB90 Backplane where I can add Modules But how can I add a Module to a standalone community ? Where is my error ? Which page did I miss/not understand ? If however I chose to enter a 8-Slot Hub Backplane as a Community to the DECagent90 I get an empty Backplane where I can configure my Bridge in any slot I want and I am able to manage it ????? Thanks for any Help/clarification OTTO (I thought I knew how to manage a Hub etc....)
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3273.1 | try this... | ULYSSE::YLOUPC::LOUIS | Wed Feb 14 1996 06:11 | 18 | |
>> ... any Help/clarification The following is not a "clarification" but maybe a Help. I don't know if there is a better solution, however, this is how I do and it's works : - In the "community of current agent", add a 8-slots with the adequate communities r/w, and make it current. - in the empty 8-slot, add a bridge with the adequate information. Must be added in slot 7 or 8. - go back to the community table and change the hub type of index2 to "standalone" - apply and make current your bridge will make it appear as standalone module (If it doesn't work the 1st time, make current the agent90, and re-make current your standalone bridge90). good luck | |||||
3273.2 | I owe You something | PRIVAT::OTTO | getting better all the time | Wed Feb 14 1996 09:37 | 7 |
Hello Louis, thank You very much for this tip I did the trick.. OTTO |