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 took the DECagent 90 (V2) in our office out to a customer site to demo HUBwatch with my laptop on their LAN. I put the DECagent 90 in their DH90. It only had a DS90L+. This was my first time accessing this agent with my laptop. When the hub came up on the screen, it had modules that were not in that hub but were the modules in the hub back in the office. Is there something I should have done to the DECagent 90 to reset it? And if there is, does this reset the IP address as well? Thanks, Dave
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
891.1 | We're supposed to remember these things! | ROGER::GAUDET | Because the Earth is 2/3 water | Fri Apr 08 1994 10:05 | 12 |
Modules for which the DECagent 90 proxies are retained under the following conditions: 1) The module was manually added via an SNMP manager (e.g. HUBwatch) 2) The module has had SNMP sets done to it such that its present configuration is not that of its "default" configuration (e.g. a repeater was auto-discovered and has since been given port names and/or had ports disabled). You can simply delete the unwanted modules from the customer's hub using HUBwatch. ...Roger... |