| Title: | FDDI - The Next Generation |
| Moderator: | NETCAD::STEFANI |
| Created: | Thu Apr 27 1989 |
| Last Modified: | Thu Jun 05 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2259 |
| Total number of notes: | 8590 |
Cross posted in FDDI notes file and HUB_mgnt Customer is running HP Openview Node Manager 3.3 on HPUX DECconcentrator 500 and DECconcentrator 900 are on the network. All digital mibs are from gatekeeper.dec.com MIBs loaded include: DEC-elan-v29 RFC1512 When doing system info is done, results are: ..dec.ema.15.5.1 - for DC500 V3.1 ..dec.ema.15.5.4.1 - for DC900 V2.0 If in addition to the above mibs, DEChub90-v2 mibs are loaded the results are: ..dec.ema.emasystem.5.1 - for DC500 V3.1 ..dec.ema.emasystem.5.4.1 - for DC900 V2.0 What other mibs are missing? and why is the DEChub90 mibs being used for DC500 and DC900. The concentrators show up on the map like ethernet devices on a straight line instead of ring. Raj Singapore
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1436.1 | No such MIB. | 56822::GALLAGHER | Thu Sep 08 1994 14:11 | 9 | |
This question was answered off-line. Raj asked how he could compile the definitions for the "15.5.1" and "15.5.4.1" sysObjectID numbers. My answer is that there should be a MIB containing all the sysObjectIDs for all DEChub products, but there is not. I mailed Raj a *very* rough draft of the DEChub sysObjectID's MIB which should help. I don't expect to release the MIB until after the next wave. -Shawn | |||||