| Page 36 of 39 |
| ||||||
|
|
|
|
|
|
|
| |
| Message |
|
|
|
| Description/Action |
| |
|
|
|
|
|
| the traps for the FS to catch the traps. The driver only catches traps |
| |
|
|
|
|
|
| for configured Nodes. 5 |
| |
|
|
|
|
|
| The server side of the driver could not complete parsing a message. |
| |
| SNMP:#31 | Err Couldnt | parse | Immediately after this message the driver prints a hex dump of the |
| |||
| msg: found %#x at %d |
| offending message. The driver prints this error when the SNMP |
| ||||
|
|
|
|
|
| message contains a field that is not supported by the driver.7 |
| |
|
|
|
|
|
| If the driver is configured as a Server agent then a remote Client |
| |
|
|
|
|
|
| may try and walk the FieldServer. To do this the driver requires one |
| |
|
|
|
|
|
| or more specially named Data Arrays. |
| |
|
|
|
|
|
| DA_SNMP_n where n=1,2,3,4 etc |
| |
|
|
|
|
|
| • | DA_SNMP_1 corresponds to 1.3.6.1.4.1.6347.1 |
|
|
|
|
|
|
| • | 1.3.6.1.4.1.6347.1.0 corresponds to the 1st element of |
|
| SNMP:#33 Err. Too many DA's |
| DA_SNMP_1; 1.3.6.1.4.1.6347.1.1 corresponds to the 2nd |
| ||||
| to validate for SNMP. Max=%d |
| element of DA_SNMP_1, etc. |
| ||||
|
|
|
|
|
| • | DA_SNMP_2 corresponds to 1.3.6.1.4.1.6347.2 |
|
|
|
|
|
|
| • The length of the DA determines how many OID’s correspond to |
| |
|
|
|
|
|
|
| each DA. |
|
|
|
|
|
|
| To allow a walk the FS must, have at least DA_SNMP_1. There is a |
| |
|
|
|
|
|
| maximum limit of 1000 on the number of these DA’s. The DA’s must |
| |
|
|
|
|
|
| be numbered sequentially.Error! Bookmark not defined. |
| |
|
|
|
|
|
| If the FieldServer is configured as a SNMP Client you may ignore |
| |
|
|
|
|
|
| this message, If you have configured the FieldServer is configured |
| |
| SNMP:#34 FYI. No DA's for walk | as a Server then any attempt by a remote client to ‘walk’ the |
| |||||
| by remote browser |
| FieldServer will fail because there are none of the specially named |
| ||||
|
|
|
|
|
| Data Array’s required to respond to the walk. Read the notes for |
| |
|
|
|
|
|
| Msg #33. |
| |
| SNMP:#35 |
| FYI. | DA |
|
|
| |
| 'SNMP_DA_1' is missing. Walk |
|
|
| ||||
| will fail |
|
|
|
|
|
|
|
| SNMP:#36 FYI. 'SNMP_DA_%d' |
|
|
| ||||
| is missing. Walk will fail |
|
|
|
| |||
| SNMP:#37 FYI. No SNMP DA's | Read the notes for Msg #33. There are no DA’s suitable for a walk |
| |||||
| for walk by remote browser. | by a remote client. |
| |||||
| SNMP:#38 | FYI. | DA | names | If the FieldServer is configured as a SNMP client, ignore the |
| ||
| suitable for walk by remote | message. If the driver is configured as a Server then read MSg #33. |
| |||||
| browser |
|
|
|
|
|
|
|
| SNMP:#39 FYI. Use an array |
|
|
| ||||
| called | <%s> | to | expose | Read 0 |
| ||
| diagnostic info |
|
|
|
|
| ||
|
|
|
|
|
| If you allocate a Node_ID to the SNMP Node it must be a number in |
| |
| SNMP:#40 Err. Bad Node_ID - | the range |
| |||||
| forcing to 11 |
|
|
| 11. Node_ID’s are used when Node_Status bits are prepared. |
| ||
|
|
|
|
|
| Refer to Enote43 on the FST Web Site. |
| |
|
|
|
|
|
| The driver has rejected a Map Descriptor because the parameter |
| |
| SNMP:#41 | Err | Undefined | called ‘SNMP_Trap_Store_Method’ has been set to indexed/lookup |
| |||
| SNMP_OID_Index1 |
| and the driver requires that the parameter ‘SNMP_OID_Index1’ is |
| ||||
|
|
|
|
|
| defined. Refer to Appendix A.28 |
| |
| SNMP:#42 | Err | Undefined | The driver has rejected a Map Descriptor because the parameter |
| |||
| SNMP_OID_Index2 |
| called ‘SNMP_Trap_Store_Method’ has been set to indexed/lookup |
| ||||
7Refer to Enote 63 on the Website for more information
8Edit the configuration file, download 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