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.

Silver

LMS 2.5.1 - RME 4.0.4 - 24 Hour Inventory Change Report

Every day I get this report. It always contains 1 or 2 devices, every day another. I'm trying to figure out what is interesting in these reports. So far I have not been able to so.

The sysuptime has changed.... a couple of seconds. The system clock had deviated a bit and is now synchronized with the time server....only this device...tomorrow another one etc

The amount free and used ram changed... a couple of bytes. Normal right? Load fluctuates, so does memory.

Then I see the interfaces? No, I get hit with the interface indexes (why is that, anyone?)

I suppose these interfaces changed because the time on the machine has changed?

Why can't I even see the status went from up to down? Or if it remained up or down.

I have a problem explaining the use of these reports to my customers. And I do feel this report should indicated that there might be a problem, but the bogus reports like the one I get every day, will prevent the sysadmin from noticing it.

It will just disappear in the noise.

Comments anyone? Am I missing the point?

Cheers

Michel

7 REPLIES
Silver

Re: LMS 2.5.1 - RME 4.0.4 - 24 Hour Inventory Change Report

A sample report

Silver

Re: LMS 2.5.1 - RME 4.0.4 - 24 Hour Inventory Change Report

Does anyone get usefull 24 Hour Inventory Change Reports?

Cheers,

Michel

New Member

Re: LMS 2.5.1 - RME 4.0.4 - 24 Hour Inventory Change Report

I have the same problem.

It doesn't seem to be isolated to one particular model of hardware either. Our 3750's, 6509's & AP's all randomly flag the faults that you listed above.

I'd be interested if Cisco are have any suggestions to make the report slightly more meaningful?

Cisco Employee

Re: LMS 2.5.1 - RME 4.0.4 - 24 Hour Inventory Change Report

A sysUpTime change is useless. Free and available memory may also be useless. Interface last change time could be interesting. This indicates that the interface had a state change at the given time. A state change could mean the interface was bounced (see the ifLastChange description in the IF-MIB).

As for making these reports more useful, it would be a good idea to disable what you don't need or don't care about. This can be done under RME > Administration > Inventory > Inventory Change Filter. Here you select the items you DO NOT want to monitor for changes.

For example, for this report, I would check System:SysUpTime and Memory Pool:Free (MB) and Memory Pool:Used (MB). Playing with these filters can usually get you a set of inventory change reports that make sense for your organization.

Silver

Re: LMS 2.5.1 - RME 4.0.4 - 24 Hour Inventory Change Report

Joe, Nige,

Thanks for your responses.

For the report to become useful certain things should change.

Sysuptime can be very interesting because it can indicate a reboot/reload of a device.

If suddenly my free mem goes from 30% to 5% I would like to know.

I feel a realistic threshold value before a detected change triggers a change report is what we need here.

If an interface bounces comes up or goes down I'd like to know what interface had this problem. But I need to know if it came up went down or bounced, and I don't want to go out and match an ifIndex to an existing interface, I want to see it's name and description.

With regards to disabling the monitoring of certain changes I noticed that even if I don't monitor Interface: Last Changed , I still monitor Operational and Admin State. That makes me feel I can safely try to disable this. I assume the fact that I only see "Last Changed" indicates that the interface state has not changed.

I'm please to know that all the relevant parameters are monitored but the report definitely requires some adjustments

I'm looking forward to hear about the improvement Cisco has in the pipeline for this type of reports.

Cheers,

Michel

Cisco Employee

Re: LMS 2.5.1 - RME 4.0.4 - 24 Hour Inventory Change Report

For reloads, the RME reloads report might be more useful. For a large dip in free memory, DFM can report on that. RME is not a fault management tool per se, so I don't see threshold capability being added to this report. I think the goal of the inventory change report is to report on hardware changes for the most part.

However, if you wanted to persue adding a thresholding feature per object, contact your account team to build a business case for it using a PERS request.

Silver

Re: LMS 2.5.1 - RME 4.0.4 - 24 Hour Inventory Change Report

The problem is that I don't wish to fire more reports at my customers.

The more reports, with more bogus alerts, the bigger the possibility that a real event gets ignored.

I may pursue this change request, after all, this is my point, the hard work, collecting the data, is already done.

All it takes is getting some "common sense" in the report generation

The issue with network management is not getting events and notifications!

The issue is to make the important ones to get noticed!

RME is not for fault management, I know. But DFM is not the most ideal fault management system either.

When the network gets bigger you need something that correlates the events to find the root cause.

Cheers,

Michel

201
Views
11
Helpful
7
Replies
CreatePlease login to create content