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 |
Hi, Can anyone say if there is any point in putting a DECagent90 into a DEChub 900 ? Should it allow you to manage DECrepeaters if there is a DECbridge 90 installed as well ? I put my DECagent V1.1 in the 900 and it didn't see any modules at all. Is this expected behaviour ? I know this may sound a bit dumb... unfortunatley my customer has been sold this configuration. He doesn't have Hubwatch to manage the repeaters, so I can only assume that whoever sold him the agent thought that it would allow him to manage them. Thanks, Alan Lloyd TSC Basingstoke.
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
642.1 | Ok for backward compatibility purposes... | QUIVER::SLAWRENCE | Thu Jan 20 1994 16:08 | 8 | |
The DEChub 900 will allow a DECbridge 90 to become the hub master iff the 900 MAM has _NOT_ been given any IP address. If you factory reset the MAM (or just clear both IP addresses and then reset it) you should see 'hub master' displayed on the slot for the bridge. You have to do all the usual things to configure the bridge and the DECagent90 as if they were in a DEChub 90, of course. | |||||
642.2 | thanks | KERNEL::LLOYDA | Don't worry... Be Happy ;^) | Fri Jan 21 1994 05:43 | 11 |
Hi, I tried this and it worked first time. We had a DECserver 900 in the hub and the agent said that it was "unknown", will this be fixed in v2.0 of the agent s.w ? Many thanks, Alan Lloyd. LAN Technologu Group, CSC Basingstoke. |