| 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,
1. Is there a way to manage a multistack90 system full of
DECrepeater90T16's and one 90TS, without using the UTP management cable?
(I mean via the thinwire ethernet segment)
2. Can the simple SNMP managament applications other than our clearVISN
manage DECrepeater90T-16's via the thinwire ethernet segment?
I ask these because the network is very long (more than 420m which is
the limit for UTP management cable).
Thanks,
- Onder.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3841.1 | STRWRS::KOCH_P | It never hurts to ask... | Thu Sep 05 1996 17:53 | 10 | |
1. No, 90T16s don't have an IP address, therefore they can't be managed
via Ethernet.
2. No again.
3. Are you saying this because you are using fiber between the modules?
If so, put a 90FS at each end and use that as the SNMP manager for the
stack. If not, can you explain more about the 420m limit since thinwire
is limited to 185 meters.
| |||||
| 3841.2 | You're right, fiber will be there. | ISTWI1::EKER | Fri Sep 06 1996 08:29 | 11 | |
Thanks for the response.
3. Yes, there'll be fiber link between buildings, but instead of using
two 90FS's, we are considering to connect the fiber to 1 90FS and 1
90T-16's AUI port. That's why I was asking whether we can manage the
repeaters through the ethernet. So we'll be using 1 90FS for the 1st
building, 1 90TS for the second building (it will be better because you
gain some more UTP ports also).
| |||||
| 3841.3 | STRWRS::KOCH_P | It never hurts to ask... | Fri Sep 06 1996 12:14 | 3 | |
I thought so. You need either an DECrepeater 90TS or 90FS to be the
stack manager. Your conclusion is one that I do all the time.
| |||||