FieldServer FS-8704-09 SNMP Computer Drive User Manual


 
FS-8704-09 SNMP Driver Manual Page 37 of 39
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
Message Description/Action
and the driver requires that the parameter ‘SNMP_OID_Index2’ is
defined. Refer to Appendix A.2
SNMP:#43 Err Undefined
SNMP_Trap_Store_Method
The driver found a Map Descriptor parameter heading
‘SNMP_Trap_Store_Method’ but could not find a value for it.. Refer
to Appendix A.2
8
SNMP:#44 Err Undefined
SNMP_Write_as_Trap
The driver found a MD parameter heading ‘SNMP_Write_as_Trap’
but could not find a value for it. Refer to Appendix A.2Refer to
Appendix A.2
8
SNMP:#45 Err. Undefined
SNMP_Read_Method
The driver found a MD parameter heading ‘SNMP_Read_Method’
but could not find a value for it. Refer to Appendix A.2
8
SNMP:#46 FYI. Duplicate
state=<%s>
Refer to Appendix A.2. When adding entries to the driver lookup
table a duplicate lookup string was found. You probably did not
intend this.
8
SNMP:#47 Err. No space. Driver
rejects value state=<%s>
value=%d
Refer to Appendix. You are adding entries to the driver lookup table
and the driver has run out of space. If you need more entries
contact the FST sales group.
SNMP:#48 FYI. Added
state=<%s> value=%d
This message is for information only. The driver prints it each time a
new entry is added to the lookup table. Refer to Appendix A.2
SNMP:#49 Err. Cant find lookup
table entry below
Refer to Appendix A.2. The driver has been told to store data from a
trap using the lookup method. The search string was extracted from
the trap but a matching entry could not be found in the table. If the
data is required, a new entry for the table will need to be created.
8
SNMP:#50 Err. Found non-string
data while extracting string
Refer to Appendix A.2. The driver is building the search string by
extracting data from the trap. The search string is built by extracting
data from two OID fields which should be formatted as strings. A
non-string has been found. To resolve this issue you will need to
reconfigure the agent that produced the trap.
SNMP:#51 Err Indexed Store.
Offset too big to store
DAOffset=%d IndexOffset=%d
Off=%d DA=%s Len=%d
Refer to Appendix A.2. The driver is storing data using the lookup
method. The offset into the data Array that corresponds to the
search string points beyond the end of the Data Array. You may
need to increase the length of the Data Array or change the offset
value associated with the search string.
8
SNMP:#52 FYI. Lookup=%s:%s
Value=%d DA:Off=%s:%d
This message is for information only. Each time the driver stores
data using the lookup method this message is printed so that you
can see the effect of the trap.
SNMP:#53 FYI Cant send trap
with null string. DA=%s Off=%d
You are trying to send a trap with Ascii string data but the when the
Data Array was inspected for data to form the string it found a zero
in the 1
st
location and hence it thinks the string is empty. Make sure
the data array has some data to form the string.
SNMP:#54 Err. Diagnostic
DIAG_USER_1 - Bad TRAP
Length
An internal diagnostic has been generated. Take a log and call Tech
Support.
9
SNMP:#55 Err. Multiple Objects
Rquested.
The server can respond to polls for multiple objects in one SNMP
message. Re-configure your SNMP client.
SNMP:#56 Err. Needs Data
Array with name=%s
The server has received a poll for data. The polled OID corresponds
to the named Data Array. The driver can’t find the Data Array. Either
reconfigure the remote client to poll for an appropriate point. Read
Appendix A or correct the configuration adding the new Data Array.
9
Refer to Enote 63 on the Website for more information