Dev Spectrum: 9.3 H01 on RHEL/Solaris

All,

I am certifying new traps and noticed that since upgrade from 9.2H09 to 9.3H01 
I am seeing all Unicode characters (because of internationalization) in 
EventDisp and PCause, which is making it difficult to read/edit them when on 
the server.

So I would like to know - What do you use to read the files on servers (I don't 
want to use MIB tools to read/edit these files).

We do a lot of traps certification and I really don't want to stand up an old 
release of Spectrum just for this.


Sample EventDisp and PCasue file for utf8 - en_us


{d "%w- %d %m-, %Y - %T"} - A "tmxHardwareFailure" event has occurred, from {t} 
device, named {m}.\u000a\u000aThis trap is issued if the network element has 
detected a \u000a      fatal hardware fault.\u000a      trapPerceivedSeverity - 
'critical'; otherwise - 'cleared'\u000a      additional trap information: slot 
# \u000a                                   hardware failure.\u000a              
                     port # or processor Id\u000a                               
    pid # or encoder #\u000a
trapIdentifier = {I 1}
trapSequenceId = {I 2}
trapNetworkElemModelNumber = {S 3}
trapNetworkElemSerialNum = {S 4}
trapPerceivedSeverity = {T trapPerceivedSeverity 5}
trapNetworkElemOperState = {T trapNetworkElemOperState 6}
trapNetworkElemAlarmStatus = {T trapNetworkElemAlarmStatus 7}
trapNetworkElemAdminState = {T trapNetworkElemAdminState 8}
trapNetworkElemAvailStatus = {T trapNetworkElemAvailStatus 9}
trapText = {S 10}
trapNETrapLastTrapTimeStamp = {G 11}
trapChangedObjectId = {o 12}
trapAdditionalInfoInteger1 = {I 13}
trapAdditionalInfoInteger2 = {I 14}
trapAdditionalInfoInteger3 = {I 15}
(event [{e}])


TMX HARDWARE FAILURE\u000aSYMPTOMS:\u000aThis trap is issued if the network 
element has detected a \u000a      fatal hardware fault.\u000a      
trapPerceivedSeverity - 'critical'; otherwise - 'cleared'\u000a      additional 
trap information: slot # \u000a                                   hardware 
failure.\u000a                                   port # or processor Id\u000a   
                                pid # or encoder #\u000aPROBABLE 
CAUSES:\u000aRECOMMENDED ACTIONS:\u000a1) Refer to the Event Message associated 
with this alarm for additional details that the device may have provided about 
the cause of this condition.\u000a\u000a2) Review the Events associated with 
this model that occurred in the same time frame as this alarm in order to gain 
insight into the device's state.  These can be viewed from the Events tab in 
OneClick.


Saurabh Bohra
Sr. Network Mgmt Systems Analyst
ESPN Inc.
O: 860-766-0842  |  M: 860-385-3597  |  e-mail: saurabh.bo...@espn.com


---
To unsubscribe from spectrum, send email to lists...@unc.edu with the body: 
unsubscribe spectrum arch...@mail-archive.com

Reply via email to