LMS 3.2 DFM Fault History purge Job

Hey experts,
the Online Help for LMS 3.2 say "Data for Fault History remains in the DFM database for 31 days".
How can I increase or reduce the amount of days the data will remain in the DFM Fault History Database?
Is it possible to have only 10 Days in Fault History or can I set it up to 60 Days?
Is there a specific config file which could be edited for my purposes?
I know the purge Job for Fault Hostory but it purges the data which is older than 31 days, I can´t adjust this job.
thx,
Patrick

No, this is immutable.  The only thing you can change is the TIME at which the purge happens.

Similar Messages

  • LMS 3.2 Syslog purge job failed.

    We installed LMS 3.2 on windows server 2003 enterprise edition. RME version is 4.3.1. We have created daily syslog purge job from RME> Admin> Syslog> Set Purge Policy. This job failes with the following error.
    "Drop table failed:SQL Anywhere Error -210: User 'DBA' has the row in 'SYSLOG_20100516' locked 8405 42W18
    [ Sat Jun 19  01:00:07 GMT+05:30 2010 ],ERROR,[main],Failed to purge syslogs"
    After server restart job will again execute normally for few days.
    Please check attached log file of specified job.
    Regards

    The only reports of this problem in the past has been with two jobs being created during an upgrade.  This would not have been something you would have done yourself.  I suggest you open a TAC service request so database locking analysis can be done to find what process is keeping that table locked.

  • LMS 3.2 DFM and PPP interface traps

    Hello,
    I have a problems with traps from PPP links. Traps are corectly send from device, LMS server receive traps, but these traps are not displayed in DFM. I'm using SNMPv2c (SNMPv3 doesn't work properly). Information about link down is corectly diplayed in DFM syslog, but I have not any informations in a Fault History.
    Can you help me?
    Regards,
    Martin

    DFM doesn't process link down traps except to determine if a link is flapping.  You will not see link down traps in the DFM Alerts and Activities Display.  Instead, DFM will use SNMP and ICMP polling to determine if an interface goes down.  This will not happen for all interface types, though. These PPP interfaces may be learned as dial-on-demand interfaces by DFM, and thus will not report when they go down.  If these links should be up all the time, then you will need to customize an interface group in DFM to match these interfaces, then enable the desired threshold information for these interfaces.  You will still not see link down traps in DFM, but DFM should show OperationallyDown events in AAD based on the polling it does.

  • How to delete old events in fault history?

    hi,
    I wanted to delete all my old alerts in DFM. I am aware that ciscoworks has only last 31 days events/alers in the fault history, which basically would be in the database dfmfh.db. My problem here is that i have more than 183000 alerts in the fault history for a month, I dont wanted all of these alerts now.
    /gopi

    There is no way to control the amount of time data lives in Fault History.  As you pointed out, data will be retained for one month.  You can reinitiatize the Fault History database, but that would destroy all FH data.

  • Ciscoworks LMS 4.0 DFM Custom Traps

    Hello,
    We want to use Ciscoworks LMS 4.0 for Access Control List Monitoring. i.e. if we end the ACLs with "log" entry, we may send  the ACL deny logs to the Ciscoworks as Syslog or Snmp Trap format.
    With "debug snmp packets" command we may observe the packets are sent to the LMS, but the traps don't show up as alarms. Is it possible to observe any trap entry with LMS DFM Fault Manager by customizing the module, because we think the engine of the DFM analyzes the traps and shows some of the traps, not all of the traps are observable.
    The command output is as below:
    Thanks in Advance,
    Best Regards,
    Mar  2 10:28:30.028: SNMP: Queuing packet to 10.10.10.1
    .Mar  2 10:28:30.028: SNMP: V1 Trap, ent ciscoSyslogMIB.2, addr 10.10.20.1, gen  trap 6, spectrap 1
    clogHistoryEntry.2.742 = SEC
    clogHistoryEntry.3.742 = 7
    clogHistoryEntry.4.742 = IPACCESSLOGDP
    clogHistoryEntry.5.742 = list 191 denied icmp   10.10.10.1 -> 10.10.20.1 (0/0),   10 packets
    clogHistoryEntry.6.742 = 69082382

    DFM consumes the traps and decides based on its built-in code-book what to do - rise one of the predefined Events or just silently ignore it. The best DFM can do is forward the trap as-is to another trap receiver.
    Perhaps the LMS Syslog-Server can do what you want and lauch automated actions (like scripts or e-mail) based on certain criteria.
    But you should take care of the underlying syslog file and keep its size under control with logrot.pl utility.
    The online help of LMS should give you more details on the syslog capabilities or this link to the LMS 4.0 Administration Guide:
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.0/user/guide/admin/useNotif.html#wp1075603

  • Cancel Auto-Purge Job?

    Is there a way to cancel an Auto-Purge job? The process is a background process MMON so I can't kill it using kill session.

    I started with that note over a week ago. The cancel task worked for the shink task but the delete task I finally killed after 2 days because it had generated 33 gigs of undo and I couldn't tell when it might finish. (It was trying to remove over 30Gigs of data from wri$_adv_objects.)
    I've been struggle with this problem for a while now and finally decided to just turn off loggin to wri$_adv_objects and its index and delete from the wri$_adv_objects (over 187 mil rows) where the task_id = 14128 (since that's the sql that was showing when I tried the dbms_advisor.delete_task) - this is the shrink task id that is taking up so much space.
    That was going well yesterday (I had the delete statement in a loop deleting 100k rows at a time then committing). but then this auto-purge job kicked in last night and put a lock on wri$_adv_objects so I had to kill my little delete script. I can't restart my little delete script until this auto-purge job finishes, in the mean time it's generating redo at an enormous rate.

  • LMS 4.0 - a fault annotation

    Hi,
    the customer uses LMS 4.0. He annotated one fault and he cleared this fault. So this fault was cleared and it wasn't seen in the fault monitor. For now the fault is again active and the annotation for this fault is shown. So my question is: Does DFM have some annotation database where all anotation of faults are saved? When the same faults re-occur and the annotation was made for this fault in history - this fault will be displayed with this annotation??
    Thank you.
    Best Regards
    Roman

    The annotations are saved to a specific event.  If the event re-occurs, that event will have a new ID, so the annotation will not be there.  Annotations are saved in the dfmEpm database.

  • LMS 3.2 DFM Event Summary problem

    Hi all,
    I have two issues, and one question:
    Issues:
    1)
    In the DFM portlet, under DFM Evnets Summary I see a list stating that I have 2 devices that have Event Name as Duplicate. When I click on the number 2, it opens up Device Fault Manager - Alerts and Activities, but it's show with no records. This has been like this for quite some time now... Any ideas on how to fix this?
    2)
    I've got 5 devices in DFM that are in the DFM Device Status as Questioned. They don't exist in CS, RME nor any other place. I went to DFM Device Management and under Rediscover/Delete, and was going to delete the devices from DFM, but the delete button is grayed out. How can I remove the devices from DFM?
    And now for the Question:
    I sometimes get an event in DFM Alerts and Activities that looks like this:
    Name                                                          Value
    Event_Description:               InformAlarm
    Component:                         [FQDN DEVICE NAME REMOVED]: Cisco Configuration Management Trap
    Description:                         Cisco Command Monitoring -> Event Command Source: SNMP, Event Config Source: Running, Event Config Destination: Network TFTP
    Sometimes it gets cleared by it self... So I'm a bit interested to find out what does this event mean? and how to get rid of it?
    Any help is appreciated
    Gudvardur

    It sounds like your DFM databases may have gotten out of sync with the rest of LMS.  You can clear the first two problems by following the steps in https://supportforums.cisco.com/docs/DOC-8796 to reinitialize the dfmEpm, dfmInv, dfmFh, DFM.rps, and DFM1.rps databases.  Do not reinitialize the others.
    As for the delete button being grayed out, this is expected when DFM is in auto-manage mode.  To activate this button, go to DFM > Device Management > Device Import and disable auto-manage mode.
    The config management trap you're seeing will occur whenever the config changes on the device.  This event should clear on its own.

  • LMS 4.2.2 Fault manager does not resolve hostname for some devices

    This is Cisco Prime LMS 4.2.2 on Windows 2008 R2
    As far as I understand it Fault Manager need to be able to do reverse lookup for ip adresses to show the correct name in the "device name" column. I have double and tripple checked and all devices that only is shown as an ip address do have a reverse in the dns used by the LMS server.
    The device is correctly registered and inventory have been run. If I hold the mouse pointer over the crosshair on the row of the offending device all info is shown including correct device name and fqdn.
    The server is upgraded from 4.2.1 to 4.2.2 and we have the same problem before the upgrade.

    The problem may occur if the lookup was not possible when the device was added to fault management. 
    Faultmanager, unlike the rest of LMS, does not update the display name.
    If the resolver.pl in /opt/CSCOpx/bin is able to get the device name, then resolution is fine.
    The only workarrounds are to the delete the device from LMS and re-add it, or use cli tools on the server to remove and re-add the device from the DFM repository.
    Cheers,
    Michel

  • LMS 4.2 - DFM devices stuck in "Learning" state

    Hi,
    Does anybody know why this same kind of bug/error/software fault exist in LMS 4.2 as it was in LMS 3.2 ? Why after a while after discovery of devices (state is "Known") DFM drops the state of devices to "Learning" and it stucks forever. Restarting of daemon manager helps for a short time. It looks like the processing of faults stops a while after discovery is complete.
    LMS 4.2 is running on Solaris 10, connected to other LMS in DCR Slave configuration.

    The connection between the ciscoworks GUI and the DFM repository is not 'optimal', or something like that. It's complicated.
    What could cause the behavior you mention however, is either someone rediscovering devices that are still in learning state, or the presence of multiple active rediscovery schedules.
    You may even delete all schedules excepts the default redisovery schedule which you can/should suspend. If the problem then stays away you know what caused it.
    At this stage any device that really changes must be rediscoverd in DFM manually.
    I think Admin -> Fault takes you to a page showing the schedule, if not lookup 'fault rediscovery schedule' in the help.
    Cheers,
    Michel

  • LMS 4.2.2 Fault Discovery - Network Adapters Limit Exceeded

    Running fault device discovery after adding approx 50 new devices to LMS DCR. It seems I have reached a limit in DFM with regards to how many device components it can manage. The devices are put into questioned mode and the following error is seen in the Question State Device Report
    Network Adapters Limit Exceeded.The number of Network Adapters discovered by Fault Management exceeded the maximum supported limit.Please check on screen help for more information.     
    What is the limit that is being referred to here? Is it independent of the LMS device licence? Where can I see how many "network adapters" LMS is monitoring? I have approx 900 devices being managed by LMS on a 1500 device licence. I am running LMS 4.2.2
    Any light you could shed on this would be appreciated
    Thanks,
    Mark         

    I've come across this a few times. I did not find a solution. It went away with a reinstall.
    What seems to happen is that somehow DFM puts all the device interfaces in a managed state.
    It should not.
    It should only manage the ports and interfaces that connect to another managed device.
    There is a hardcoded limit of 40.000 managed ports in DFM.
    Suspected situations:
    On one server where I found this the system locale that I put to us-english, was somehow put back to be-french. Maybe even during the installation, not sure who or what did this.
    On another server the anti-virus which I  had turned off, was turned back on during installation,probably by a policy server.
    Cheers,
    Michel

  • LMS 4.2 - DFM operation ?

    Hi,
    I'm wondering what is required for DFM in LMS 4.2 to work properly. I've migrated it from LMS 3.2.1 an it was quite easy to set up : tie master and slave server with DCR, allow some ports (icmp, snmp) for DFM and the discovery process started without a problem.
    Now, I have same configuration (the server is the same) but it looks like DFM is not going to allocate any devices and is not going to start discovery at all. They are present in CS but DFM is not seeing them. What could be preventing DFM from starting?
    Greets,
    Tomek

    The connection between the ciscoworks GUI and the DFM repository is not 'optimal', or something like that. It's complicated.
    What could cause the behavior you mention however, is either someone rediscovering devices that are still in learning state, or the presence of multiple active rediscovery schedules.
    You may even delete all schedules excepts the default redisovery schedule which you can/should suspend. If the problem then stays away you know what caused it.
    At this stage any device that really changes must be rediscoverd in DFM manually.
    I think Admin -> Fault takes you to a page showing the schedule, if not lookup 'fault rediscovery schedule' in the help.
    Cheers,
    Michel

  • Cisco Prime LMS 4.2 DFM Devices Missing

    Hi Everybody
    Having manually added a device into the DCR and confirmed that it's in a managed state I cannot get added into DFM.  Within Device Centre, it's collector status against "Data Collection", "Inventory", and "Fault Discovery" are all Success.
    My Device Allocation Policy (Inventory > Device Administration: Device Allocation Policy) is currently set to Manage All Devices.
    Running "geti Router" from within dmctl -s DFM returns all but the device in question.
    I have manually deleted and readded and have also restarted service CRMDmgtd.
    Many Thanks in anticipation.

    Hi,
    can you try to remove it from DB as below ::
    NMSROOT/Objects/smarts/bin/dmctl -s DFM invoke <Class>::<Instance>  remove
    Class => Switch or Router,
    Instance => Device IP or Name.
    dmctl> invoke Switch::X.X.X.X remove
    then add the device back in LMS and see if it makes any difference.
    Also try to increase the SNMP timeout and retry for DFM:
    Admin > Network > Timeout and RetrySettings> FaultManagement SNMP Timeouts and Retries
    Thanks-
    Afroz
    ***Ratings Encourages Contributors ***

  • LMS 3.1 - DFM Issues

    Hi There,
    I'm having a few problems with my setup, some more important than others, but causing troubles for me all the same (I've listed them in priority)
    1) Right now I have the default Scheduled rediscovery set in DFM to run weekly. That's all well and good, except that when it runs, less than 10 of my 664 devices get put into the "known" state, while the rest - after 6-8 hrs - get thrown into the "questioned" state. When I try to suspend the schedule, I get an error (see attached: rediscovery_error.jpg, and associated Rediscovery.txt). I have a case open with the TAC right now about this, but it has not been resolved. The only fix I have at the moment is to rebuild the DFM DB, then re-add all the devices, and then I have to unmanage all the interfaces/ips that I'm not using. Seems like an incredible waste of time.
    2) When adding a new device to the DFM (automatically pulled when I add it to the DCR) all the existing devices return to their default managed/unmanaged state. Again, at this point, I have to go back and unmanage all the interfaces/ips, etc... (May be related to above, I'm not sure.)
    3) My jrm.log file is currently sitting at over 650MB (not KB). This equates to roughly 7.3 million lines of text, where 99% of the lines are "Test Exception is : java.sql.SQLException: JZ0S2: Statement object has already been closed." (see attached: jrm.jpg)
    4) I would also like to know if the emails that are sent out by the DFM can be changed - a lot of the information included in them is not relevant to me, and I would like to add the information that is.
    I've also attached the output of pdshow and systeminfo, which seems to be the first thing most people are asked for.
    I'm running LMS 3.1, with an updated DFM (3.1.3) on Windows 2003 Enterprise.
    Please let me know if there is anything else I can provide that may help.

    I should also point out that once you upgrade to LMS 3.2, there is a consolidated patch for DFM to apply at http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=3.2.0&mdfid=282640771&sftType=CiscoWorks+Device+Fault+Manager+Patches&optPlat=Windows&nodecount=2&edesignator=null&modelName=CiscoWorks+Device+Fault+Manager+3.2&treeMdfId=268439477&treeName=Network+Management&modifmdfid=&imname=&hybrid=Y&imst=N&lr=Y which will fix quite a few DFM bugs which are still present in 3.2.  You should download, and apply this patch, and that should give you a much better DFM experience.

  • LMS 4.0 - Invisible faults

    Since I installed LMS 4, the Faults panel at the top of the screen always reports 4 critical faults. When I click on the red icon to go to the Fault Monitor, I get "No faults are available" (screenshot attached).
    Anyone know how to fix this?
    Thanks

    The quickest way is to reinitialize the DFM databases by following the instructions in https://supportforums.cisco.com/docs/DOC-8796 .  However, if you want a more tactical analysis you can open a TAC service request, and they can go through the dfmEpm database to look at why these counters are wrong.  The counters should be showing the total number of events, which are the atomic conditions occurring on the devices.  This would not necessarily line up to the alerts seen at the top level of the Fault Monitor.  However, in your case since you don't see any alerts, you shouldn't have any events.

Maybe you are looking for

  • Scanner icon lost HP LaserJet Pro 100 color MFP M177fw

    HP Model:  HP LaserJet Pro 100 color MFP M177fw After "updating" drivers on my IMac my Scanner disappeared and I have not been able to Scan for over a month.  I just started a new business and this is debilitating!  Can anyone shed any light on this?

  • Platform version5.0.1 is not compatible with miniversion =6.0.2 in English

    Have just trried to do the recent Firefox upgrade from ver 5 to ver 6.0.2 under XP service pack 3 with all updates and received the following error platform version5.0.1 is not compatible with miniversion >=6.0.2 in English I cannot now get firefox!

  • I lost my home folder all my settings are gone. like i have a new Mac.

    I was cleaning up the icons on the left side of the screen under the bar. My Rheta/Home icon was not there, nor was the Desktop, even the Computer icon was gone. In moving Pictures, Movies, Documents, Desktop and Rheta/Home back in the order I though

  • Sound Blaster Audigy 4 pro optical In probl

    Hello, I recently purchase a audigy 4 pro, My current setup is 3 wires(green, black, orange) going from my Logitech X-530 5. speakers to the audigy 4 sound card, from there, the AD_Link and Ad_Link2(firewire) going to the Audigy's External I/O, now w

  • MIGO in case of multiple account assignment.

    Hi, I have created PO with multiple account assignment. AAC is P. While doing MIGO, FI document is not getting generated. Can anyone plz explain how multiple account assignment functionality works? Regards Nilesh