Maintainence Logs

[james1982]

Can anyone advise what the errors below mean, thanks in advance: We recently changed the IP Trunks from a DPNSS link to MPLS, unsure if this is anything to do with it????????????

Log Type: Maintenance
Log Number: 1935
Severity: Warning
Date: 2009/Mar/24
Time: 08:24:41
Source: Call Control - Maintenance
Description: Maintenance: Category(General); msgFormatId(0) Call over XNET TRUNK 0360 dropped by Loop Avoidance Digits dialled by caller : 5050 Caller's extension :
Module: Main
File Name and Line Number: Maintenance;0


and

All Maintenance/Software Logs

Log Type: Maintenance
Log Number: 1461
Severity: Warning
Date: 2009/Mar/22
Time: 02:36:57
Source: FLOOD_MONITOR

what is a flood monitor alarm????

 

[iheardrain]

I'm am having the same issue!

 

[MitelInMyBlood]

LOOP AVOIDANCE as it's name might imply is a feature of the PBX to drop a call that is ping-ponging back and forth between two nodes. Example, user on node 1 ext 5000 has his phone forwarded to user on node 2 ext 6000. Similarly the user on node 2 ext 6000 has his phone forwarded to ext 5000 on node 1.

A call presented to either 5000 or 6000 would thus spin infinitely in a loop, back and forth between the two systems, tying up all your trunks were it not for loop avoidance. With loop avoidance the above call scenario will still spin, but only for a specific number of forward hops after which the call will drop. The max number of forward hops is a programmable number in your system options assignment form. Pick any value between 2 and 10. (Hint use 1 + the total number of nodes you have). With 2 nodes set it for 3.

The scenario can also occur when you make a mistake programming your ARS tables or when there are programming errors in OPS_MAN, especially when the errors in OPS are deleted by an idiot rather than tracked down and corrected by a properly-trained tech.

As for your FLOOD MONITOR log, I have never seen that before. We use MPLS between multiple locations so that shouldn't be an issue.

Logs severity class of "Warning" are merely informational in nature and not service-affecting.

 

[IrwinMFletcher]

Flood Monitor is a routine that checks to see if there is a 'flood' of unwanted traffic on the system, usually related to a denial of service attack or a rouge router.

Do a FloodShow from the shell and see what it says.

 

[kwbMitel]

I have seen the flood warning when my customers have accidently exposed the Voice Lan to Data Traffic.

It will usually be followed by packet loss warnings and ultimately a system reset.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.