| 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 |
Can a DECbrouter 90 in a DEChub manage a DECrepeater in a manner similar to that performed by a DECbridge 90? Roy
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 345.1 | pointer | CONSLT::BUZZELL | Fri Aug 20 1993 18:00 | 5 | |
NO. See note 270.
| |||||
| 345.2 | other options | TMAWKO::PRESSLEY | pin heads are people too... | Wed Aug 25 1993 00:57 | 2 |
The decagent should attain this capability in a future release.
Also the dechub 900 can manage the repeater without any assistance.
| |||||
| 345.3 | Does the Integral Manager provide left hitchcock ? | TENTO1::GREENR | Curiosity Killed The Cat | Tue Sep 14 1993 20:29 | 12 |
Is this really true ??
Although the PID states that the Integral management module provides
SNMP proxying for DECrepeater 90's and Hub Services the DEChub/HUBwatch
documentation implies that a DECrepeater 900TM is required to provide
hub management services. ie The integral management card does the
proxying but the 900TM acts as bus master talking left hitchcock to
DEChub 90 style repeaters.
Can someone clarify this please ?
regs
ross
| |||||
| 345.4 | DECrepeater 900TM used to provide a path for IP to the hub mgt module | NAC::FORREST | Tue Sep 21 1993 21:25 | 11 | |
The DECrepeater 900TM is needed to provide an in-band path to the DEChub 900 Management module, since the management module has no MAC interface. We call this function IP Services; other 900 repeater modules are planned to provide IP Services too. The hub management module actually polls each slot and, upon detecting a DECrepeater 90, will proxy for it and support the same MIB objects as does the DECagent 90 when it proxies for a DECrepeater 90. jack | |||||