The Netview server will display this string in hex because it does not
understand the characters.
it "assumes" that what it is getting is something like a MAC address and
displays it all in hex, because it has no idea which characters are
significant and which aren't.
I had the same problem with snmp traps that did not ahead to the snmp
standard and included funny characters.
The solution I used was to pass the trap to a script which translatored the
hex to acsii and then used wpostemsg to send the correct readable message to
the TEC server.
Marcel
marcel.rafter@unisys.com
Novell Technical Specialist
Unisys NZ.
-----Original Message-----
From: Eirik Tysse [mailto:eirik.tysse@DNB.NO]
Sent: Friday, 7 May 1999 01:30
To: NV-L@UCSBVM.UCSB.EDU
Subject: Trouble with special characters in rulesets.
Hi
In norway we use the special characters æ-ø-å pritty much (i hope they show
up all right !)
Example: "Open" in English is "Åpen" in Norwegian.
When sending an snmp trap including any of these characters, the words look
fine in the eventlog/trapd.log,
but not from the $NV_ATTRx in the rulesets.
The whole string looks like garbage.
Example: When sending an octetstring with the word "Åpen", it looks like
this: 0xc570656e
Has anyone else experienced something similar ?
NV 5.1.1 on solaris 2.6
Regards,
Eirik Tysse
DnB IT-Driftstjenester/NSM-Center
Tel: 55223592 - Fax: 55223450
mailto:eirik.tysse@dnb.no
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the virus programs used
in the DnB Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
|