Mullaparthi> I was trying to write a small tcl script using scotty
Mullaparthi> extensions. In trying to construct a varbind list for a
Mullaparthi> Trap, I used the following: [list tpAlarmCatName {OCTET
Mullaparthi> STRING} "rose"]
Mullaparthi> I get an error which says "illegal octet string value".
Mullaparthi> But the man page for snmp gives a few examples in which
Mullaparthi> it directly uses text. Everything works fine if I use
Mullaparthi> [list tpAlarmCatName {OCTET STRING} "72:6f:73:65"]
Mullaparthi> (basically the hex representation for "rose").
Mullaparthi> Do I have to convert my text strings to hex
Mullaparthi> representation everytime?
The primitive representation which will always work is "72:6f:73:65".
However, if there is a MIB definition for the object-type
(tpAlarmCatName in your example) and this MIB definition uses a
textual convention with an appropriate DISPLAY-HINT clause, then
scotty will interpret the DISPLAY-HINT and accept "rose".
Juergen
-- Juergen Schoenwaelder schoenw@ibr.cs.tu-bs.de http://www.cs.tu-bs.de/~schoenw Technical University Braunschweig, Dept. Operating Systems & Computer Networks Bueltenweg 74/75, 38106 Braunschweig, Germany. (Tel. +49 531 / 391 3289)-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.