| 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 |
In a DecHub900 if each device does not have IP address of its own
you can still look at all port status/counter information using
hubwatch..
but if you use SNMP command "snmpwalk" to walk thro' the dechub900
it does not show any port/status information of each device and device
ports. You can get this information only if you snmpwalk on the
device itself, which means each device have its own IP address
my question is what mechanism is used in hubwatch to get all the
status/counters information of each device in a hub which does not
have its own IP address.
Thanks in advance
Radha
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3204.1 | NETCAD::DRAGON | Thu Jan 25 1996 12:39 | 6 | ||
Radha,
Use the slot community string (ie public-6 for slot 6, etc.) and
the hub's IP address.
Bob
| |||||
| 3204.2 | Community String Multiplexing | NETCAD::GALLAGHER | Fri Jan 26 1996 10:48 | 15 | |
Adding just a bit to what Bob said.... The mechanism is called community-string multiplexing. The MAM's community is, by default, "public" and all DEChub900 modules (except the DECserver900TM) are manageable by sending messages to the MAM using community strings: "<mam community string>-<slot number>" (e.g. "public-6" for the module in slot 6). This allows you to manage the hub using only one IP address. What going on internally is that SNMP messages are being translated by the MAM and sent to the appropriate modules. The modules replies are then translated back into SNMP and relayed back to the Network Management Station. -Shawn | |||||