Page 34 of 39 |
| ||||||||||
|
|
|
|
|
|
|
| ||||
Appendix C. Driver Error Messages |
|
| |||||||||
|
|
|
|
|
|
|
|
|
|
|
|
|
| Message |
|
|
|
|
|
| Description/Action |
|
|
|
|
|
|
|
|
|
|
| A response from the remote device reports an error. The message |
| |
|
| SNMP:#01 Err. Response report |
| is good but inside the message there is a field reporting an error. |
| ||||||
|
| err=%d |
|
|
|
|
|
| Consult the vendor for the meaning of the printed SNMP error |
| |
|
|
|
|
|
|
|
|
| number. |
|
|
|
| SNMP:#02a/b Err. | Could | not |
| The driver found an error in the message structure preventing it from |
| ||||
|
|
| extracting the SNMP version number. See msg #05 for follow up |
| |||||||
|
| read SNMP response version |
| actions. |
|
| |||||
|
|
|
|
|
|
|
|
|
|
| |
|
| SNMP:#03a/b | Err. | Version. |
| This driver only supports SNMP version #1. See msg #05 for follow |
| ||||
|
| Expected=1 Rcvd=%d |
|
|
| up actions |
|
| |||
|
| SNMP:#04a | Err. | Extract | Int |
| The driver is extracting an integer value from the SNMP message |
| |||
|
| Failed. Index=%d |
|
|
|
|
| but the field was incorrectly formatted. Formatting can be checked |
| ||
|
| SNMP:#04b | Err. Expected | INT. |
|
| |||||
|
|
| using Ethreal4 |
|
| ||||||
|
| Found NULL. Index=%d |
|
|
|
|
|
| |||
|
|
|
|
|
|
|
|
| The driver is attempting to process a SNMP message that is not |
| |
|
|
|
|
|
|
|
|
| correctly formatted; contains an error or contains unsupported |
| |
|
|
|
|
|
|
|
|
| SNMP elements. Immediately after the message has been printed |
| |
|
| SNMP:#05 | Err. | Parse | Failed. |
| the driver does a hexadecimal dump of the message. |
| |||
|
|
| If you see this message rarely and data is being transferred correctly |
| |||||||
|
| MD=%s Msg Buffer |
|
|
|
| then ignore it. If it is repeated or affects data transfer then take a log |
| |||
|
|
|
|
|
|
|
|
|
| ||
|
|
|
|
|
|
|
|
| and call tech Support. This message is usually preceded by a |
| |
|
|
|
|
|
|
|
|
| message which provides a more specific clue as to why the parse |
| |
|
|
|
|
|
|
|
|
| failed.4 |
|
|
|
| SNMP:#10 | FYI. NuDesign | MIB |
|
|
|
| |||
|
| File=%s created. (Tier=%d) |
|
| These messages do not require any corrective action provided that |
| |||||
|
| SNMP:#10 | FYI. | Custom | MIB |
|
| ||||
|
|
| they report what you expected. They are printed for confirmation |
| |||||||
|
| File=%s created. (Tier=%d) |
|
| only. |
|
| ||||
|
| SNMP:#10 | FYI. | MIB | File=%s |
|
|
| |||
|
| created. (Tier=%d) |
|
|
|
|
|
|
| ||
|
| SNMP:#11 | Err. |
| Can’t | open |
| The configuration has told the driver to build a customized MIB file. |
| ||
|
|
|
| This requires that a file called MIBHead.ini is present on the |
| ||||||
|
| MIBHead.ini. Producing std MIB |
| FieldServer. Refer to the configuration manual and Appendix A.3 for |
| ||||||
|
| file |
|
|
|
|
|
| more information. |
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
| SNMP:#12 Err. Bad MD length - |
| A MD was found where the length was not specified or specified as |
| ||||||
|
| defaulting to 1 |
|
|
|
|
| zero. Specify the length setting it to one. 5 |
|
| |
|
| SNMP:#13 | Err. | Max=255 |
|
|
|
| |||
|
| number | of | TRAP |
| map |
| The default maximum number of trap Map Descriptors is 255. |
| ||
|
| descriptors exceeded |
|
|
|
|
|
| |||
|
| SNMP:#14 | Err. | SNMP_TRAP |
|
|
|
| |||
|
| map descriptor must have OID |
|
|
|
| |||||
|
| specified |
|
|
|
|
|
| You must specify the ‘SNMP_OID” parameter on a Map Descriptor |
| |
|
| SNMP:#15 Err. Passive_Client |
| used for a trap. Read Appendix A for more information on Traps5 |
| ||||||
|
| map descriptor must have OID |
|
|
|
| |||||
|
| specified |
|
|
|
|
|
|
|
|
|
|
| SNMP:#16 |
|
| unknown |
| The only permitted value for the | SNMP_Read_Method is |
| ||
|
| SNMP_Read_Method value: %s |
| ‘walk’Error! Bookmark not defined. |
|
| |||||
|
| SNMP:#17 Err. Diagnostic 1 |
| The driver has executed an internal diagnostic. If this message is |
| ||||||
|
|
| printed please call Tech Support. |
|
| ||||||
|
|
|
|
|
|
|
|
|
|
|
4Refer to Enote 63 on the Website for more information.
5Edit the configuration file, downloaded the modified file to the FieldServer and restart the FieldServer for the changes to take effect.
FieldServer Technologies 1991 Tarob Court Milpitas, California 95035 USA Web: www.fieldserver.com Tel: (408) 262 2299 Fax: (408) 262 9042 Toll Free: (888) 509 1970 email: support@fieldserver.com