| 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 |
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 |
|---|---|---|---|---|---|
| 1370.1 | NACAD::GALLAGHER | Fri Sep 02 1994 12:22 | 35 | ||
>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 This is because the DEChub90 MIB contains a definition for emaSystem, while the "DEC Vendor MIB" does not. >What other mibs are missing? and why is the DEChub90 mibs being used for >DC500 and DC900. You've compiled a definition for emaSystem. The definition came from the DEChub90 MIB. Openview is using this definition when decoding the sysObjectID retrieved from the products. This may be a small MIB consistency issue - but you've encountered the full extent of the problem, that sysObjectIDs may be printed differently. This would not lead to other problems (like the way devices are drawn on maps). >The concentrators show up on the map like ethernet devices on a straight line >instead of ring. The statement has nothing to do with anything previously mentioned. I don't see how decoding a sysObjectID has anything to do with how a map is drawn. I suspect you'll have to tell Openview that the device is an FDDI concentrator. (It could figure this out by reading the FDDI MIB, but I doubt it's that sophisticated.) -Shawn | |||||
| 1370.2 | No such MIB. | NACAD::GALLAGHER | Thu Sep 08 1994 14:12 | 10 | |
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 | |||||