| 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 specialist that is EXPORTING an XYPLEX server SNMP entity
INTERFACE 1 data. In the characteristics for INTERFACE 1 is the
attribute "ifPhyAddress", which is the ethernet address of the server
that does TCP/IP. She states that the exporting of this child SNMP
entity doesn't include this attribute in her RDB file. All the other
attributes are there. She has installed the XYPLEX extended MIBs.
Is this a bug or feature with any of the INTERFACE 1 ifPhyAddress?
Any help will be appreciated..
RO
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2736.1 | bug | DANZO::CARR | Fri Apr 10 1992 11:57 | 12 | |
We know that exporter has problems exporting attributes if the datatype in out_p does not exactly match the datatype in the dictionary (i.e the MS file). This has been discussed elsewhere in the MCC notes conference. The snmp am is returning the wrong datatype for this attribute, and for a couple of others too (atPhysAddress,ipNetToMediaPhysAddress). This will be fixed. Thanks for pointing out this problem. | |||||
| 2736.2 | More on snmp exporting | TMBKTU::ANGELILLO | Thu Apr 16 1992 11:39 | 8 | |
I am the specialist who reported the problem. To make this totally clear, exporting snmp entity data in DECmcc v1.1 is useless. There is no identifier associated with the data exported which identifies which snmp entity I have exported. Will this be fixed in V1.2? My customer is not pleased. We have exported data for him and written reports for mux devices and the vitalink translans. He also wants his xyplex terminal servers defined as snmp entities to export. What is the possibility of a workaround or a patch? | |||||