| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I have a customer who wishes to support private MIB extensions from the
DECmcc SNMP AM. Although there should not be any problems in doing so
I have a couple of questions:
If the customer has the MIB extensions (written in ANS-1) what will be
the easiest mechanism for making these extensions known to DECmcc?
What will this mechanism involve? (relinking the MIB? manual
intervention?)
How long is the process of making the MIB known to DECmcc likely to
take? (I know this depends on how detailed the extension is, but any
ball-park figures would be gratefully accepted).
Thanks,
John
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1031.1 | Private MIBs supported in V1.2 | BSYBEE::EGOLF | John C. Egolf LKG2-2/T02 x226-7874 | Mon May 20 1991 12:56 | 14 |
John, Support of private MIB extensions is supported in V1.2, not the current version. In V1.2, the user will be prompted for the ASN.1 file name and, barring any problems with it, it will be sucked into DECmcc. The wall time may be from 5 mins to an hour, but the time the customer needs to spend will definately be a few mins. Wait for V1.2 and we'll have concrete info for you. EFT target is late July/early Aug. JCE | |||||
| 1031.2 | Just what I wanted to hear! | ARRODS::GILLJ | John, DTN 847-5849 | Mon May 20 1991 13:31 | 2 |
Thanks John, just the answer I wanted.
| |||||