| 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 got the following question from a DEChub 900 customer. Can
someone give me some ideas to answer it?
I need to change the community strings associated with all of the
boards in DEC900 chassis to the same value, in order to manage them
effectively with Spectrum. It's not evident to me from reading the
MIB or looking at HubWatch, that this can be done, since the community
strings seem to be generated by appending the slot number to the
chassis community string. Is there any way around this?
thanks,
Ted
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3863.1 | Do the 900 module support in-band management? | NETCAD::GALLAGHER | Thu Sep 12 1996 09:25 | 24 | |
Maybe. The DEChub900 has a feature which allows you to manage devices in the hub using a single IP address. This simplifies setup, and conserves scarce and valuable IP address. The technique used is called, "Community String Multiplexing" and, as you know, it involves appending a "-<slot-number> to the Hub Manager's community string and using the Hub Manager's IP address. Most DEChub900 modules can also be assigned an IP address of their own. This is called "module in-band management". Modules which support in-band management can be assigned IP addresses and community strings via the setup console. So if you give the module an IP address of its very own, then it can be managed both via: Hub Manager's IP address <Hub Manager's community>-<slot num> Module's IP address <Module's community> I'm really surprised to hear that Spectrum can't handle this since I know that Cabletron also using community string multiplexing in their chassis. -Shawn | |||||