T.R | Title | User | Personal Name | Date | Lines |
---|
643.1 | | SLINK::HOOD | I'd rather be surfing | Thu Jan 20 1994 14:22 | 5 |
| It varies, but for most devices it's ifDescr is the port name.
Or charPortDescr. Or...
Tom Hood
HUBwatch
|
643.2 | all mibs are published | QUIVER::SLAWRENCE | | Thu Jan 20 1994 17:02 | 12 |
| The ports (other than the OBM port) are on the module, not on the hub;
so you need to query the module for them.
To address a module in the hub, use the hub community for the module.
If the community you are using for the hub is 'public', then the
communtiy for the module in slot 3 is 'public-3'.
The port information is in the usual places for the device.
For more details on the community/slot mechanism, see note 581.2 and
the DEChub900 Hub Manger MIB (available on gatekeeper as
DECHUB900-HUBMGR-MIB-V1-0.TXT )
|
643.3 | NO data from charPortDescr... | ZTOIS1::VISTA | Renato VISTA, MCS/SPS France/Strasbourg | Fri Jan 21 1994 03:15 | 18 |
|
To .1,
Hi Tom,
ifDescr seems to be not used for storing Port Name.
charPortDescr doesn't seem to exist in any mibs POLYCENTER Netview
brings.
Any other idea ?
Futher, is it possible to know where statistic/counters information are
stored ?
Thank you for help.
Renato
|
643.4 | to .2, any EASYnet pointer ? | ZTOIS1::VISTA | Renato VISTA, MCS/SPS France/Strasbourg | Fri Jan 21 1994 03:17 | 12 |
|
To .2,
Hi,
is it possible to get this MIB file on EASYnet ?
Thank you.
Renato
|
643.5 | lots of MIB variables. All of them are public. | SLINK::HOOD | I'd rather be surfing | Fri Jan 21 1994 14:00 | 9 |
| re .3
For specific implementation questions, please contact the HUBwatch team
directly. There are a *lot* of MIB variables used in HUBwatch. All of
the MIBs are publicly available.
Tom Hood
HUBwatch
226-6776
|