Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

LMS Prime: Disabling Alterts for BRI Interfaces

Hello,

i revceive a lot of Alerts of BRI Interfaces on a router.

EVENT ID               = 000072X

TIME                   = Tue 08-Nov-2011 16:06:44 CET

STATUS                 = Active

SEVERITY               = Critical

MANAGED OBJECT         = 192.168.25.4

MANAGED OBJECT TYPE     = Routers

EVENT DESCRIPTION       = OperationallyDown::Component=IF-192.168.25.4/36 [BR0/0/0:1];ComponentClass=Interface;ComponentEventCode=1075;AdminStatus=UP;DuplexMode=FULLDUPLEX;OperStatus=DOWN;MaxSpeed=64000;Type=DS0;Mode=NORMAL;IsFlapping=false;InterfaceCode=CODEUNKNOWN;LastChang

NOTIFICATION ORIGINATOR = Fault Management Module

how can i get rid of them?

i already searched in Monitor > Fault Settings > Setup > Threshold Settings

but i didn't found where i can disable Operationally Down messages for certain interfaces.

thanks

alex

5 REPLIES

LMS Prime: Disabling Alterts for BRI Interfaces

The faults you get come from the bearer-channels. You don't want to monitor these. You do want to monitor the signaling interfaces to know the BRI or PRI is working.

Check the end of this post where Joe explains the syntax of a file you can use to filter these interfaces when DFM faultmanagement discovers the devices.

https://supportforums.cisco.com/message/3431258#3431258

Cheers,

Michel

New Member

LMS Prime: Disabling Alterts for BRI Interfaces

Hi Michel,

i tried to modify the tpmgr-param.conf file and added this entry IFDescrPattern-.1.3.6.1.4.1.9.1.1045 *~Bearer Channel*. But still I receive the messages.

#This is an example of how to restrict the creation of ports for a

#specific sysObjectId based on the ifType:

#IFTypePattern-SwitchPort.1.3.6.1.4.1.9.1.501 53

IFDescrPattern-.1.3.6.1.4.1.9.1.1045 *~Bearer Channel*

# Add Fiber Channel port (56) for MDS devices

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.12.3.1.3.380 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.12.3.1.3.376 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.12.3.1.3.375 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.12.3.1.3.414 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.12.3.1.3.411 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.12.3.1.3.442 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.12.3.1.3.612 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.12.3.1.3.719 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.1.475 6|26|56|62|69|117

IFTypePattern-SwitchPort.1.3.6.1.4.1.9.1.407 6|26|56|62|69|117

LMS Prime: Disabling Alterts for BRI Interfaces

I think the patern should be like this:

IFDescrPattern-.1.3.6.1.4.1.9.1.1045 ~*Bearer Channel*

Is it only this sysobject ID send the message?

Cheers

Michel

New Member

LMS Prime: Disabling Alterts for BRI Interfaces

Hi Michel,

yes its the only Router which has BRI Interfaces, all the others have PRI and they don't send this kind of messages.

Do i have to restart the daemon manager after changing the parameter?

regards

alex

LMS Prime: Disabling Alterts for BRI Interfaces

Yes,

I think a rediscovery of the device(s) is required as well.

Cheers,

Michel

673
Views
0
Helpful
5
Replies