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. And see here for current known issues.

New Member

LMS 4.1 alerts on unused sereal interfaces

Greetings,

I have been getting alerts on unused serial ports on my routers as being operational down.  How can I stop these alerts?  Thank you.

Phil.

5 REPLIES

LMS 4.1 alerts on unused sereal interfaces

Put the interfaces admin down and let DFM/faultmanagment rediscover the devices.

Cheers,

Michel

New Member

LMS 4.1 alerts on unused sereal interfaces

Is there any other way, than this?  Most of these serial interfaces can not be configured.  When I try to access the interface I do get the following:

xxxxx(config)#int se0/0/0:5

%Cannot access B-channel interfaces

Thanks.

Phil.

LMS 4.1 alerts on unused sereal interfaces

Yes Phil,

I tell fault management not to manage the individual pri or bri channels.

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

This however cant be done via the gui but via one of its configuration files.

Cheers,

Michel

New Member

LMS 4.1 alerts on unused sereal interfaces

Michel,

I added the following to the tpmfr.* file, stoped and started the crmdmgtd and removed and added the device without and success:

#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

#Stop monitoring the serial B-Channel on 2821,3925,2921 and 2911

IFDescrPattern-.1.3.6.1.4.1.9.1.577 ~Bearer Channel*

IFDescrPattern-.1.3.6.1.4.1.9.1.1042 ~Bearer Channel*

IFDescrPattern-.1.3.6.1.4.1.9.1.1044 ~Bearer Channel*

IFDescrPattern-.1.3.6.1.4.1.9.1.1045 ~Bearer Channel*

# Add Fiber Channel port (56) for MDS devices

LMS 4.1 alerts on unused sereal interfaces

Actually I messed arround with that for a while. Try this for the various device sysobjectid's

IFDescrPattern-.1.3.6.1.4.1.9.1.577 ~Bearer*

I think it failed over the space in the pattern

Cheers,

Michel

615
Views
0
Helpful
5
Replies
CreatePlease login to create content