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'm really sorry to ask this as it should be obvious, but I'm still confused... I've looked at the configuration guide and am a little clearer, but nto quite good enough... My customer has several (about 8 or so) DEChubs throughout their plant. They are purchasing the DECwatch software for a VAXstation to manage these. Most of these hubs have bridges (fiber), though not all of them. The hubs are NOT daisy chained. They are located on different floors/loations throughout. My questions are as follows: 1. What's the story on V1.1 of the DECagent? Are bridges still necessary to manage repeaters within a hub. Can they now manage repeaters (90T's and 90C's) as long as the agent is in the hub with the repeaters to be managed or is a bridge still necessary within this hub? 2. If one agent can manage up to 4 daisy chained hubs, how many non daisy chained hubs can it manage? Most hubs in this location have a 90T and a 90C repeater in them which adds up to a max of 182 devices/hub (in the current config). Again, each of these has a bridge so isit one agent/bridge? or one agent/xx devices? I know these questions seem rather basic, but basic is what I need. Thansk for the help Cindy
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
305.1 | One agent, eight 8-slot hubs | QUIVER::GAUDET | Tue Jul 20 1993 12:15 | 15 | |
Cindy, 1. Yes, you still need a bridge to manage repeaters in the hub. Direct backplane support for managing repeaters did not make it into V1.1 of the agent. This support is planned for V2.0. 2. One DECagent can manage up to eight 8-slot DEChub 90s. However, you will need a bridge in each hub to do management of repeaters in that hub. What you will need to do is define a unique set of community strings (read-only and read-write) for each hub you want the agent to manage. This can all be done via HUBwatch. I assume that all these hubs are on the same LAN (i.e. no routers between hubs)? ...Roger... | |||||
305.2 | distance limitations (other than enet) | ODIXIE::RICHARDSON | Are we there yet?? | Wed Jul 21 1993 09:31 | 6 |
Thanks - that clears things up. They are all on the same LAN with no routers. It is, however, a pretty large fiber optic LAN. I am assuming there are no restriction as to the distance limitations of the decagents to the hubs that they are managing. I guess if the LAN is operating within fiber limitations, the agents will operate just fine? | |||||
305.3 | No other limitations that we know of | QUIVER::GAUDET | Wed Jul 21 1993 12:44 | 6 | |
.2> decagents to the hubs that they are managing. I guess if the LAN is .2> operating within fiber limitations, the agents will operate just fine? We certainly hope so! :-} ...Roger... |