cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
770
Views
5
Helpful
2
Replies

LMS 3.2 DFM "null" parameters in Email notification

Hello everyone

I'm recently facing odd problem with DFM email notification. In some email messages fields "ALERT ID", "MANAGED OBJECT" and "MANAGED OBJECT TYPE" are "null". For example (I've changed unrelated private data to X and made null bold):

From: X

Sent: Friday, November 19, 2010 3:26 PM

To: X

Subject: 0019P4I ; null ;Fri 19-Nov-2010 15:25:40 CET ; Critical ; HighQueueDropRate ; Active ;

EVENT ID                = 0019P4I

ALERT ID                = null

TIME                    = Fri 19-Nov-2010 15:25:40 CET

STATUS                  = Active

SEVERITY                = Critical

MANAGED OBJECT          = null

MANAGED OBJECT TYPE     = null

EVENT DESCRIPTION       = HighQueueDropRate::Component=IF-X/1 [Fa0/0] [Do C2AOMIL port GigabitEthernet0/1 (Trunk 802.1Q)];ComponentClass=Interface;ComponentEventCode=1053;Type=ETHERNETCSMACD;OutputPacketQueueDropPct=2.3153992  %;MaxSpeed=100000000;OutputPacketQueueDropRate=1.6511111  PPS;OutputPacketNoErrorRate=69.65889  PPS;QueueDropThreshold=1;InputPacketQueueDropPct=0.0  %;InputPacketNoErrorRate=70.80555  PPS;DuplexMode=FULLDUPLEX;InputPacketQueueDropRate=0.0  PPS;

CUSTOMER IDENTIFICATION = X

CUSTOMER REVISION       =X

I've attached nos.log and NOSServer.log files.

If anyone solved this problem or has any idea what could be wrong please let me know.

Best Regards,

Przemek Przytula

1 ACCEPTED SOLUTION

Accepted Solutions
bdarwish
Beginner

after upgrading to LMS 3.2.1 the problem was resolved.

View solution in original post

2 REPLIES 2
Joe Clarke
Hall of Fame Cisco Employee

This looks like it might be related to CSCtj68588.  If you click on the "Open Service Request" link in the Actions panel in this thread, you can open a TAC SR with the Cisco Support Community thread data attached to it.  Your TAC engineer should be able to provide you a patch to correct this.

bdarwish
Beginner

after upgrading to LMS 3.2.1 the problem was resolved.

View solution in original post