[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
2248.0. "SNMP Table access fails on SINTROM" by LARVAE::POETT () Fri Jan 31 1992 13:05
We have recently worked with Sintrom Datanet in the UK who produce
a network quality analyser (SNMP POD) to monitor the condition of
Ethernet/802.3 networks using SNMP.
The private MIB makes extensive use of tables with multiple key fields.
One example is a table containing network load history over a range of time
intervals. For example, to access their SNMP object nlh1sTable
(nlh1sTable=Network Load History 1 second Table) the date and time fields
are used as keys.
When looking into the table from the Iconic Map Operations menu the keys are
returned as two identicle hex values. e.g.
nlh1sTable (%X005C011F000E2137,%X005C011F000E2137) which translate to the date
and time.
Trying to access table entries then returns -attribute not gettable -
The suggestion from Sintrom is that we are not handling the keys correctly.
They claim to have sucessfully linked with other SNMP management systems.
Our system is DECmcc BMS V1.1, SNMP AM V1.1, VAXstation 3100 Mod 76, VMS 5.4
Thanks in advance for any help/suggestions.
Best regards,
Dave
(UK N&C DCC)
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2248.1 | | YAHEY::BOSE | | Tue Feb 04 1992 16:26 | 6 |
|
The SNMP AM can handle upto 1 octet string in a multiple key index.
Two or more octet strings in a table index will cause it to break.
I don't know if there is any plan to have it fixed for V1.2.
rahul.
|