| Page 35 of 39 |
| |||||
|
|
|
|
|
|
|
|
| Message |
|
|
| Description/Action |
|
|
| SNMP:#18 Err. Bad Send IP=%s | The IP address for a remote SNMP server (agent) has probably |
| ||||
| been incorrectly specified. Check the configuration file.5 |
| |||||
|
|
|
|
| The FieldServer cannot reach the specified remote Node. The |
| |
| SNMP:#19 | Err. | Can’t | send to | message prints the Node name and the IP address. This message is |
| |
| most commonly printed when: |
|
| ||||
| Agent/Trap Dest. %s at %s | • The wrong IP address has been specified. |
|
| |||
|
|
|
|
|
|
| |
|
|
|
|
| • The remote Node is off or in an error state6 |
|
|
| SNMP:#20 | Err. | Received | The Client side of the driver has received a request. It should only |
| ||
| set/get/getnext request |
| receive responses.6 |
|
| ||
| SNMP:#21 Err. | Bad community | The SNMP message contains a badly formatted community string or |
| |||
| string |
|
|
| the community string is absent. Read notes for msg#23 |
| |
|
|
|
|
| A response to a poll from the FieldServer contains a bound variable |
| |
|
|
|
|
| that is not supported or expected. For example an IP_ADDRESS |
| |
|
|
|
|
| and OPAQUE variable or a TRAP. Immediately after this message |
| |
| SNMP:#22 Err: Cant parse msg: | the driver prints a hex dump of the offending message. Ensure that |
| ||||
| found %#x at %d |
|
| the remote SNMP server is correctly configured. Review the Driver |
| ||
|
|
|
|
| fact Sheet for supported features. If you are confident that the FS |
| |
|
|
|
|
| should process the message correctly then capture a log and call |
| |
|
|
|
|
| tech Support. 5 |
|
|
|
|
|
|
| The Server side of the driver has received a message from a SNMP |
| |
|
|
|
|
| client which is not correctly formatted or which contains bound |
| |
| SNMP:#23 Err. Invalid Msg | variables/features not supported by the driver. | This particular error |
| |||
|
|
|
|
| message is printed when the SNMP message does not begin with |
| |
|
|
|
|
| 0x30. 5 |
|
|
| SNMP:#24 Err. Message length | The SNMP message indicates that a message length is different to |
| ||||
| error |
|
|
| the number of bytes received. 5 |
|
|
| SNMP:#25 Err. Could not get | The SNMP message number is badly formatted or absent. 5 |
| ||||
| Request ID |
|
|
|
|
|
|
| SNMP:#26 Could not get Error | The SNMP error status field is badly formatted or absent. 5 |
| ||||
| Status |
|
|
|
|
|
|
| SNMP:#27 Could not get Error | The SNMP error id field is badly formatted or absent5 |
| ||||
| Index |
|
|
|
|
|
|
| SNMP:#28 |
|
| Expected | The message header is correctly formatted but as the driver |
| |
| SNMP_TYPE_SEQ |
| continues parsing the message it can’t find the bound variables. 6 |
| |||
|
|
|
|
| Immediately after this message the driver prints the value of the |
| |
|
|
|
|
| offending OID. The driver can only serve data for configured OID |
| |
|
|
|
|
| points. |
|
|
| SNMP:#29 | ERR. | Couldn’t |
|
|
| |
| respond to Get Request for OID | The OID must correspond to a FST system OID. 1.3.6.1.4.1.6347 |
| ||||
|
|
|
|
| and there must be a data array to serve the point (read Appendix A |
| |
|
|
|
|
| for more information). To resolve this problem you will have to |
| |
|
|
|
|
| reconfigure the remote client or the FS. 5 |
|
|
|
|
|
|
| The Server side of the FieldServer can discover the IP address of |
| |
|
|
|
|
| the source Node from the IP packet header. The source Node IP |
| |
|
|
|
|
| address can also be reported inside the SNMP portion of the |
| |
| SNMP:#30 |
| FYI | Int | Ethernet message. This message is pronted if the tow IP addresses |
| |
| IP=%d.%d.%d.%d.%d Ext=%s | are different and is for information only. The driver uses the IP |
| ||||
|
|
|
|
| address contained in the SNMP portion of the message to locate a |
| |
|
|
|
|
| matching Node in the configuration. You may need to edit the |
| |
|
|
|
|
| configuration and change the IP address of the Node which sends |
| |
6Edit 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