CUOM Version 2.3 which shows multiple notifications per Device for Event with same time

[Syed Akbar Ali]

Hi CSC Team

CUOM Version 2.3 which shows multiple notifications per Device Alerts and Event with same time .

Does anyone have a solution for this problem

The message below is generated from the default All_Events for all devices

1.	Informational	0000IM6	10.28.70.100	IF-10.28.70.100/25 [E1 1/0] [AHD Connection to MOC]	OperationallyDown	17-Mar-2011 10:36:13	Cleared	00004LY
2.	Informational	0000IJ3	10.28.70.100	10.28.70.100: Authentication Failure	MinorAlarm	15-Mar-2011 19:16:42	Cleared	00004LY
3.	Informational	0000IJ1	10.28.70.100	10.28.70.100: Authentication Failure	MinorAlarm	15-Mar-2011 19:05:42	Active	00004LY
4.	Informational	0000IIY	10.28.70.100	10.28.70.100: Authentication Failure	MinorAlarm	15-Mar-2011 16:44:42	Cleared	00004LY
5.	Informational	0000IIW	10.28.70.100	10.28.70.100: Authentication Failure	MinorAlarm	15-Mar-2011 16:34:10	Active	00004LY
6.	Informational	0000IHC	10.28.70.100	10.28.70.100: Authentication Failure	MinorAlarm	14-Mar-2011 20:27:42	Cleared	00004LY
7.	Informational	0000IHA	10.28.70.100	10.28.70.100: Authentication Failure	MinorAlarm	14-Mar-2011 20:17:16	Active	00004LY
8.	Informational	0000IFS	10.28.70.100	10.28.70.100: Authentication Failure	MinorAlarm

More  event description are Minor Alarm ,Authentication Failure,OperationallyDown

Description: Interface card or network adapter operational state is not normal.

Trigger: Polling, or processed trap (see Processed SNMP Traps).

Note    For interfaces, Operations Manager will only generate an OperationallyDown clear event if the card is reinserted into the same slot, and if the module index is the same before and after the card is reinserted.

Severity: Critical.

Device Type: Host, Hub, Router, Switch, or Optical Switch.

Event Code: 1018.

Recommended Action: Check the status of indicated interface, port, or card and investigate the root cause.

Note    For interfaces, Operations Manager generates an OperationallyDown clear event only if the card is reinserted into the same slot, and if the module index is the same before and after the card is reinserted.

[Joe Clarke]

I do not see a problem here.  What I'm looking at appears to be a list of events within a common alert (which is fine).  The events all have a different time stamp.  Please describe your problem in more detail.

[Syed Akbar Ali]

I have recived multiple Severity of Warning message from one Device   Even though MOS Value = 4.4 which is detected from ITU G.107 - 1040 Sensor based voice quality.

Critical MOS Threshold

3.0

And there is no jitter & packet losses. so what cause of geneartion the Warning  message

So please advice and find below information  .

Severity

Event ID

Destination Type

Destination

IP Address

MOS

Cause

Value

Time

Codec

Source Type

Source

IP Address

1.

Warning

0000HG1

Router

x.x.x.x

x.x.x.x

4.4

N/A

N/A

22-Feb-2011 09:00:14

G711Ulaw 64k

IP Phone

xxxx

x.x.x.x

2.

Warning

0000HE2

Router

x.x.x.x

x.x.x.x

4.4

N/A

N/A

22-Feb-2011 08:49:12

G711Ulaw 64k

IP Phone

xxxx

x.x.x.x

EventID: 0000HG1
Property	Value
Destination	X.X.X.X
Destination IP Address	X.X.X.X
Destination Type	Router
Destination Model	N/A
Switch For Destination	N/A
Destination Port	N/A
Source	XXXX
Source IP Address	X.X.X.X
Source Type	IP Phone
Source Model	7911
Switch For Source	N/A
Source Port	N/A
Detection Algorithm	ITU G.107 - 1040 Sensor based voice quality
MOS	4.4
Critical MOS Threshold	3.0
Cause	N/A
Codec	G711Ulaw 64k
Jitter	0 ms
Packet loss	0 Packets
Sensor MAC	00211BFDC8FA
Number of suppressed traps	18
Suppression start time	Tue 22-Feb-2011 08:47:00 AST
Suppression end time	Tue 22-Feb-2011 08:58:00 AST

[Joe Clarke]

I'm not sure why this is happening, but this is a different issue than the original one reported in this thread.  Start a new discussion for this MOS issue to give it more attention to CUOM experts.