RME 4.0.5 - Archive Mgmt

Hi All,
I have RME 4.0.5
My Manager said there is a possiblity to trigger a mail when a device take new backup.
say example when there is any change then the device will be archived and create new version.
Now when its creating new version, will it send any mail....
Is there any ways we can configure to trigger a mail?
Regards,
Naidu.

No, this is not possible.  You could configure your system config collection jobs with an email address, and you would receive email when they run, but you would not be able to see exactly which devices had a new archive entry added.  The same could be done with when the device sends a config change syslog, but again, you wouldn't know if a new archive revision was added.

Similar Messages

  • RME 4.0.6 - Archive Purge not working

    Hi,
    I have noticed that our archive purge job is failing completely, for all devices, and it appears to have been failing for some time now.
    Looking at the meesage apeparing in the Job Details for one of the devices I get:
    *** Device Details for mydevice ***
    Protocol ==> Unknown / Not Applicable
    Unable to get results of job execution for device. Retry the job after increasing the job result wait time using the option:Resource Manager Essentials -> Admin -> Config Mgmt -> Archive Mgmt ->Fetch Settings
    The Maximum time to wait for job results per device is set to 120 seconds.
    This may explain why the job takes several days to run if every device is timing out after 2 minutes.
    My assumption, obviously incorrect, is that the purge would just go through the database and look for any archives older than a year, which is what we have set the purge options to be. This message implies that RME is trying to connect to each device.
    Is it trying to connect to each device?
    Next question would be where do I start looking so that I can fix this.
    Regards
    Jeff

    Hi Joe
    Thanks for the response. I have made the change as suggested as disabled and then re-enabled the job, so I now have it running as 8597 instead of 1106.
    JobManager.properties:
    ConfigJobManager.jobFileStorage=/rme/jobs
    ConfigJobManager.debugLevel=0
    ConfigJobManager.enableCorba=true
    ConfigJobManager.heapsize=384m
    I set this running at 9:50 this morning, and with the time now at 4:14 in the afternoon, there does not seem to be a lot happening still. If I look at the job details, all devices are in the Pending list - no Successful, or failed.
    If I look at the ..\CSCOpx\files\rme\jobs\ArchivePurge\8597\1\log file i have:
    [ Mon May 24  09:50:08 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutor,getJobExecutionImpl,160, Executor implementation class com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor
    [ Mon May 24  09:50:08 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,setJobInfo,167,DcmaJobExecutor: Initializing 8597
    [ Mon May 24  09:50:10 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutor,,119,Job listener for daemon manager messages started
    [ Mon May 24  09:50:10 NZST 2010 ],INFO ,[8597],com.cisco.nm.rmeng.config.ccjs.executor.dmgtJobRunner,run,31, DMGT Job Listener running..
    [ Mon May 24  09:50:10 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,583,Notification policy is ON, recipients :
    [ Mon May 24  09:50:11 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,603,Execution policy is : Parallel Execution
    [ Mon May 24  09:50:11 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,616,Getting managed devices list from DM
    [ Mon May 24  09:50:11 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
    [ Mon May 24  09:50:11 NZST 2010 ],INFO ,[Thread-4],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutionESSListener,run,55,ESS Message listener started
    [ Mon May 24  09:50:25 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,626,Num Threads = 1, Task = Purge Archive, Num Devices = 2696
    [ Mon May 24  09:50:25 NZST 2010 ],ERROR,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,sendMail,949,sendEmailMessage: Null recipient list
    [ Mon May 24  09:50:25 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,run,212,Job initialization complete, starting execution
    [ Mon May 24  09:50:25 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,,113,Constructing ExecutorThread DcmaJobExecThread 0
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,handleMultiDeviceExecution,143,JobExecutorThread - MultiDeviceExec DcmaJobExecThread 0 : Running
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,purgeArchive,706,Purging Archive....
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-8],com.cisco.nm.rmeng.dcma.client.ConfigArchivePurger,purgeConfigs,177,PURGE SETTINGS: ByVersion = false ByAge = true PurgeLabelledFiles = false
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-8],com.cisco.nm.rmeng.dcma.client.ConfigArchivePurger,purgeConfigs,201,Purge files between start time and Fri May 29 09:50:26 NZST 2009
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-8],com.cisco.nm.rmeng.dcma.client.ConfigArchivePurger,purgeConfigs,207,Num Versions to keep = 0
    [ Mon May 24  09:50:26 NZST 2010 ],INFO ,[Thread-8],com.cisco.nm.rmeng.dcma.client.ConfigArchivePurger,purgeConfigs,208,Purge files older than 12 Months
    [ Mon May 24  10:33:50 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,handleMultiDeviceExecution,149,Completed executeJob(), updating Results
    [ Mon May 24  10:33:50 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,getNumCyclesToPoll,1018,getNumCyclesToPoll Function Started.
    [ Mon May 24  10:33:50 NZST 2010 ],INFO ,[Thread-7],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecThread,updateMultiDeviceExecResults,781,Awaiting Job results: req Id = 0 Poll time = 2022 min(s)
    [ Mon May 24  12:39:42 NZST 2010 ],INFO ,[Tibrv Dispatcher],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutionESSListener,onMessage,66,Listener waiting for message :
    [ Mon May 24  12:42:48 NZST 2010 ],INFO ,[Tibrv Dispatcher],com.cisco.nm.rmeng.config.ccjs.executor.CfgJobExecutionESSListener,onMessage,66,Listener waiting for message :
    Is this normal? Most of the other jobs at least give you an updated success or failure for the devcies.
    Regards
    Jeff

  • Config Archive Mgmt failed LMS 3.2

    Hi
    Archive mgmt failed for 14 devices and working fine for only 2 devices..The communicaion between the LMS and Switches is through SSH,but ssh also failed.
    Thanks,

    Hey Clarke,
    Hope you;re doing well,
    i have tried from ur below instructions,i have attached logs from packet capture and the tftp permission denied error.
    Am receiving an error permission denied while copying vlan.dat file from switch to tftp server (LMS Server) same error i can see in packet capture,Is it anywhere in LMS server i have to give permission for TFTP server.
    I tried installing a different vendor TFTP server but the LMS TFTP is listening on this port.How can i disable the tftp port on LMS server and open for open vendor product such tftpd32.exe OR solarwinds tftp server.
    LMS Server IP add 10.28.73.50 and the switch IP add 10.28.72.2
    Awaiting ur reply soon.

  • LMS 3.2 factory default Archive Mgmt Exclude commands

    I'm working through LMS 3.2 initial setup and got to configuring device config commands to be ignored for alerting.
    I notice that the Archive Mgmt Exclude commands for the Device Category "Routers" has a factory default Exclude list
    "end,exec-timeout,length,width,certificate,ntp clock-period"
    However, it seems that the "Switches and Hubs" Device Category has no exclude list configured by default, so I'm getting ntp clock-period alerts for my IE3000 switches for example.
    Does anyone here have an opinion or reason why I shouldn't copy the default exclude list from the Routers category "end,exec-timeout,length,width,certificate,ntp clock-period" to the Switches and Hubs category?

    OK thanks, Joe.
    Maybe a factory default candidate for the next release?
    Actually, on this subject.  It's quite difficult to show which entries have which settings and therefore which item in the hiearchy is taking prcedence. Would be nice to have a similar kind of system ala the DFM overriding group.
    Anyway, until then
    is there some config or properties file somewhere where I can see a better overall view? (and maybe reconfigure them)   [fingers crossed]

  • LMS 3.2 RME 4.3.1 Archive Jobs hang

    LMS 3.2 Windows 2003 R2 8Gig RAM
    Managing ~4000 devices currently on LMS 3.1. Built new LMS3.2 server and patched to RME 4.3.1.
    Import from csv file works fine and RME inventory collection/ Campus Manager Data Collection all works perfectly.
    Archive Jobs hang (at random device #'s) after starting successfully.
    I have tried restarting ConfigMgmtServer process, rebooting, even reinit CMF, RME and ANI db and starting from scratch but issue persists.
    Are there any known issues with LMS 3.2 on Archive Jobs hanging or should I debug and open TAC case?

    Resolution Summary:Checked the dcmaService.log and found the following recurring statements.
    com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,406,Descr = 12.2(50)SE
    [ Tue Oct 26  15:58:45 CDT 2010 ],DEBUG,[main],com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,405,suppSysId = .1.3.6.1.4.1.9.1.927
    [ Tue Oct 26  15:58:45 CDT 2010
    Checked that the device IOS was well above the version specified in the logs, so thought may be an issue with the device packages.
    Checked the mdf version was 1.25 which came as default when we install LMS 3.2, so upgraded the mdf version to 1.45.
    Still the issue didn't got solved, so upgraded the RME device packages and now the archive job was successful.
    Message was edited by: Dheeraj Gera

  • RME 4.2 FWSM Archive Config

    We have noticed that on RME when collectoing Configs from FWSM devies that it opens 3 SSH connections to the FWSM.
    After successful collection it closes 1 but leaves the other 2 connections open for an hour.
    Why does it do 3 and why does it not terminate the other 2?
    Many Thanks
    Carl

    There have been numerous issues with RME and stale TCP sockets.  I highly recommend you upgrade to LMS 3.2 SP1 to get all of the known bug fixes.  This is a free upgrade for you.
    As for the number of TCP sockets, one is used to test for SSH and version (this is only a connection to tcp/22 and not an SSH session).  The second connection is for retrieving the config.  The third session is likely for context modules.  In this case, you're likely seeing CSCsy22242, which is fixed in LMS 3.2.

  • RME 4.3.1 not showing devices in the device select menu

    Windows Server 2008 Standard LMS 3.2 with RME 4.3.1
    When I try to select devices to check/compare device configurations in the RME Archive Mgmt menu (RME -> Archive Mgmt -> Compare Configs) no device shows up for me to select. I know the configurations are being archived because when I use the Device Troubleshooting diagnostic tool it shows me the latest configuration fetched for a device
    Since it doesn’t show me devices to select from, if I try to search for a device in the device selection, the query ends but nothing is displayed. If I select advance search I get an error window with the following message:
    Problem with File /WEB-INF/screens/deviceselector/DeviceFilter.jsp!!!Exception in JSP: /WEB-INF/screens/deviceselector/DeviceFilter.jsp:77 74: if (classtype != null && classtype.length() > 0) 75: javaClassArray = devFilterUtil.getSubClasses(classtype, false); 76: else 77: javaClassArray = devFilterUtil.getClasses(); 78: 79: 80: String javaAttributeArray[][] = devFilterUtil.getAttributes(javaClassArray); Stacktrace
    From other applications such as Ciscoview, Campus Manager, Common Services I can see all the devices configured on the system
    This was working just a few weeks ago. There have been windows updates applied to this server lately, so I’m wondering if any of them is causing the errors.
    Thanks for any information.
    Jorge Jiles

    The EssentialsDM daemon is in a waiting to initialize state, which points to CSCte49301 as a potential cause.
    Symptom:
    The EssentialsDM daemon hangs in a Waiting to initialize state (as seen in the output of the pdshow command).  Additionally, one might see "Error connecting to JRM" in Resource Manager Essentials applications.
    Conditions:
    This occurs on Windows servers after the patch for KB968930 is installed, and only if the Windows Remote Management service was started prior to starting CiscoWorks Daemon Manager.
    Workaround:
    Shutdown CiscoWorks Daemon Manager with the following command from the server's command prompt:
    net stop crmdmgtd
    Delete the following two files:
    NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib\ctmregistry
    NMSROOT\MDC\tomcat\webapps\rme\WEB-INF\lib\ctmregistry.backup
    Restart CiscoWorks Daemon Manager with the following command:
    net start crmdmgtd
    If that does not work, then the Windows Remote Management service must be stopped, and disabled.  Then, CiscoWorks Daemon Manager must be restarted.

  • LMS 3.2 Archive Update Job Failing

    The scheduled archive update job is failing for all devices. Every one that I've checked is failing with the same message:
    Execution Result:
    Unable to get results of job  execution for device. Retry the job after increasing the job result wait  time using the option:Resource Manager Essentials -> Admin ->  Config Mgmt -> Archive Mgmt ->Fetch Settings
    This setting is at 120 seconds. I've tried adjusting this setting and get same results
    Attaching job logs from most recent failure.
    Thanks for any help.

    Hi ,
    Archive purge can fail for many reasons. I can suggest few things , If it did not work. You can open up a TAC case for troubleshooting.
    Try  this :
    Increase the ConfigJobManager.heapsize as “1024m” in the following file:
    NMSROOT/MDC/tomcat/webapps/rme/WEB-INF/classes/JobManager.properties  (ie,,ConfigJobManager.heapsize=1024m)  ·
    Restart the daemon manager  ·
    Once the daemon manager is started successfully,  Go to Admin > Network > Purge Settings > Config Archive Purge Settings,  increase the “Purge versions older than:” to 12 Months  (Also configure large value  for no. of versions that you would like to have per device) and trigger the job.  ·
    Once job is completed, decrease the number of months gradually, until the desired no. of days & no. of versions required is reached.  This exercise is to reduce the number of archives loading in memory during a purge job, which will cause job hanging.
    Thanks-
    Afroz
    [Do rate the useful post]

  • LMS3.2 - Need Customized method for cofig archive to particular device.

    Hi all,
        We are using Cisco works LMS 3.2 - Added around 400 devices and monitoring the same.  Facing a issue like while taking a configuration backup getting all devcie details and also CONFIG_ARCHIEVE Job is time consuming, because getting all device configurations. To avoid this we need to know the customized method to archive target particular device configuration in the LMS 3.2 .
    Can any one help on this...Thanks in advance.
    Thanks and Regards
    Ramprakash

    This is possible. You can schedule a Archive job for perticular devices to run periodically, like every 6 hours, daily, weekly or monthly.
    This can be done from :
    RME > Config Mgmt > Archive Mgmt > Sync Archive
    -Thanks
    Vinod

  • Need to do switches configuration archive using the cisco works LMS 3.2

    Hi folks,
            We have a cisco works LMS 3.2 bundle which contains Resource Manager Essentials 4.3.0 . I am trying to do config archive of all our network switches using RME. I have no idea how to do it . so i came here ...
    Guide me what are the things to be done in both switch side and RME side.

    Hi Mohammed,
    You can do this from here :
    RME > Admin > Config Mgmt > Archive Mgmt
    check the below linlk for more information:
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_resource_manager_essentials/4.3/user/guide/config.html#wp1070778
    Thanks-
    Afroz
    [Do rate the useful post]

  • Ciscoworks LMS RME / ASA Firewall configuration pre-shared key savings

    Does anybody know the concept about saving pre-shared by Ciscoworks LMS /RME ?
    Is there a way to get the unencrypted values from Ciscoworks LMS /RME for an ASA Firewall ?
    ASA config. saved with RME
    pre-shared-key *
    ASA config. saved to TFTP from ASA
    pre-shared-key 1ZdmaKVwEkQ66nD37d9kA9fj9z75

    If you enable "shadow directory" (RME - Admin - Config Mgmt - Archive Mgmt - Archive Settings), you can find the raw configs in locations such as /var/adm/CSCOpx/files/rme/dcma/shadow/Security_and_VPN/PRIMARY on Solaris, or its Windows equivalent, after one requisite cycle of Periodic Polling and/or Periodic Collection. That's the same config one'd get saving to TFTP manually.
    However, I don't recall how to unscramble the "asterisks" in the RME GUI, if at all possible.

  • LMS 3.2 with RME 4.3.1 backup configuration problem

    Hi,
    I am faing some problems in backing up devices in the network where it shows errors.
    i am trying the to backup configuration for switches
    1-  WS-C2960-24PC-L with an ip 10.10.x.1 (10.10.11.1, 10.10.12.1, 10.10.14.1,,,,,,,,,,,,,) but it is giving me errors,  sometimes it gives:
    *** Device Details for 10.10.12.1 *** 
    Protocol ==> Unknown / Not Applicable 
    Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS 
    Execution Result:
    Unable to get results of job execution for device. Retry the job after increasing
    the job result wait time using the option:
    Resource Manager Essentials -> Admin -> Config Mgmt -> Archive Mgmt ->Fetch Settings
    i have tried to change the fetch setting but it keeps on changing it to default setting.
    and another time this output
    CM0151 PRIMARY STARTUP Config fetch failed for 10.10.14.1 Cause: TELNET:
    Failed to establish TELNET connection to 10.10.14.1 - Cause: Authentication failed on device 3 times.
    PRIMARY-STARTUP config Fetch Operation failed for TFTP.
    Could not detect SSH protocols running on the device
    Failed to fetch config using RCP.Verify RCP is enabled or not. 
    Action: Check if protocol is supported by device and required device package
    is installed. Check device credentials. Increase timeout value, if required.
    2-   WS-C3560V2-24PS with an ip 10.10.x.2 (10.10.11.2 ,,,,,,) with error that i have to check the dcmaservice.log
    3-  WS-C2960-48PST-L with an ip 10.0.0.100 with error that i have to check the dcmaservice.log
    Note: the switches 3560v2 and 2960-48PST-L are showing as unknown in the DFM although i updated the DFM with the patch
    Please find the attach the dcmaservice.log , i was not able to analyz it
    Please i appreciate some help.
    Regards,
    George

    Without debugging, it's impossible to say exactly why things are failing.  However, based on the errors, I would double-check the DCR credentials for these devices and make absolutely sure you can connect to them using the DCR credentials from the LMS server.  You can confirm this by exporting the records for these devices from Common Services > Device and Credentials > Device Management.  If SSH should be the protocol that works, also try telneting to the device from the LMS server on TCP port 22.  You will get an SSH version string back.  Make sure it is one of 1.5, 1.99, or 2.0.
    The timeout problem could be symptomatic of another bug.  Restarting ConfigMgmtServer (pdterm ConfigMgmtServer/pdexec ConfigMgmtServer) may help.  The fact that the job timeout resets to the default means there is a problem with your regdaemon.xml file.  If you post this file, I can fix it for you.

  • CiscoWorks: Why all devices Sync archive only partially successful.

    Hi,
    Whenever we sync archive a device, its always partially successfull only,  and when we click partial successfull , below details appears. We have 4000 devices and all are only partially successful only Below details are from partial successful device, it has the vlan. dat and before it was working ok.
    *** Device Details for Device1 *** Protocol ==> Telnet Selected Protocols with order ==> SSH,Telnet,TFTP,RCP,HTTPS
    Execution Result: CM0062 Polling Device1 for changes to configuration. CM0065 No change in PRIMARY STARTUP config, config fetch not required CM0065 No change in PRIMARY RUNNING config, config fetch not required CM00 Polling not supported on VLAN RUNNING config, defaulting to fetch. VLAN CM0057 VLAN RUNNING Config fetch SUCCESS, archival failed for Device1 Cause: CM0005: Archive does not exist for Device1 Action: Verify that archive exists for device.
    Also If I goto e:\NMSROOT\files\rme\jobs\ArchiveMgmt\6523(JOBID) and then log, below is output from logs.
    [ Mon Nov 14  14:55:37 GMT 2011 ],ERROR,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,initJobPolicies,925,Could not configure Thread.
    [ Mon Nov 14  14:55:37 GMT 2011 ],ERROR,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,sendMail,1334,sendEmailMessage: Null recipient list
    [ Mon Nov 14  14:56:20 GMT 2011 ],ERROR,[main],com.cisco.nm.rmeng.dcma.jobdriver.DcmaJobExecutor,sendMail,1334,sendEmailMessage: Null recipient list
    I am getting below logs,please advice, how to resolve the issue.
    Thanks.
    I am using LMS 3.2.1

    Yes you are right that we have restore from backup and since then this problem occurs. We have uninstall the CiscoWorks from c: drive and install it on e:drive, due to high disk utilization issue on c: drive.
    I have checked the
    RME > Administration > Config Management > Archive Management > Archive settings and setting is already e: /CIS~1/files/rme/dcma,
    Also from dbreade, by executing the sql "select * from Config_Device_Archive" in rmeng, I can see that some file location is C:drive and orther files location is E: drive, so I have run the below sql to correct it, although it executed correctly, by I can see that Config_Device_Archive table that still some devices location is c:, others is e: drive.
    update Config_Device_Archive set
    location=replace(location,'C:\\PROGRA~1\\CSCOpx','E:\\CAPCIS~1')
    Please advice, that how to resolve this issue.
    Thanks

  • RME 4.0.6 - Baseline Compliance jobs now failing

    I have now started getting the following error when trying to run baseline comparison job:
    In the Job Browser I get Unknown appearing in the Copliant/Depolyed Devices column, and Failed in the Status column.
    When I clcik on the Unknown link, I get the Error: No compliance report available. Reason: Device(s) may not have any configurations archived.
    This is a little puzzling as it used to work (until I started to resolve the issue of the Archive Purge job failing. See discussion RME 4.0.6 - Archive Purge not working)
    The devices have at least 1 Startup config, and hundreds of Running configs archived.
    Any ideas where to start looking?
    Regards
    Jeff

    Hi Joe,
    Below is the entries from the dcmaservice.log for the job I just ran after restarting the ConfiGmgmtServer.
    [ Thu May 27  16:55:55 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.logger.ServiceLogLevelChanger,notifyLevelChange,35,publishing urn for archive.service
    [ Thu May 27  16:55:56 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.logger.ServiceLogLevelChanger,notifyLevelChange,42,published urn as archive.service-RMELogLevelChange
    [ Thu May 27  16:55:56 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaService,main,54,Initializing dummy IOSPlatform
    [ Thu May 27  16:55:56 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaService,,103,ArchivePath : D:\CSCOpx\files\rme\dcma
    [ Thu May 27  16:56:00 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.util.db.DatabaseConnectionPool,getConnection,59,Inside ICSDatabaseConnection, MAX_COUNT =20
    [ Thu May 27  16:56:24 NZST 2010 ],ERROR,[main],com.cisco.nm.xms.xdi.SdiEngine,initDtMatcher,148,java.lang.Exception: inconsistent enumeration extension SFS_SW(63)java.lang.Exception: inconsistent enumeration extension SFS_SW(63)
    at com.cisco.nm.xms.xdi.ags.imageparser.ImageType.extendWith(ImageType.java:101)
    at com.cisco.nm.xms.xdi.pkgs.SharedSwimSFS.Descriptor.g$init(Descriptor.java:26)
    at com.cisco.nm.xms.xdi.dapi.DescriptorBD.init(DescriptorBD.java:70)
    at com.cisco.nm.xms.xdi.SdiEngine.initDtMatcher(SdiEngine.java:134)
    at com.cisco.nm.xms.xdi.SdiEngine.makeNewEngine(SdiEngine.java:86)
    at com.cisco.nm.xms.xdi.SdiEngine.getEngine(SdiEngine.java:73)
    at com.cisco.nm.rmeng.dcma.cats.CATS.(CATS.java:83)
    at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.(ConfigManager.java:391)
    at com.cisco.nm.rmeng.dcma.configmanager.DcmaService.(DcmaService.java:140)
    at com.cisco.nm.rmeng.dcma.configmanager.DcmaService.main(DcmaService.java:72)
    [ Thu May 27  16:56:24 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaService,,145,Starting Baseline Migration
    [ Thu May 27  16:56:24 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaService,,149,Got Instancecom.cisco.nm.rmeng.dcma.configmanager.DcmaBaselineTemplateMigrator@13dd208
    [ Thu May 27  16:56:24 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaBaselineTemplateMigrator,checkMigrationNeeded,281,No RESTORE Happening
    [ Thu May 27  16:56:24 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaBaselineTemplateMigrator,checkMigrationNeeded,325,select count(name) from sysobjects where name in ('Config_BaseLine_Version','Config_New_BaseLine')
    [ Thu May 27  16:56:24 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaBaselineTemplateMigrator,checkMigrationNeeded,345,COUNT (No. of Baseline tables present) :1
    [ Thu May 27  16:56:24 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaBaselineTemplateMigrator,checkMigrationNeeded,361,The BaseLine Table does not Exists
    [ Thu May 27  16:56:24 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaBaselineTemplateMigrator,doMigration,163,Check Migration result false
    [ Thu May 27  16:56:24 NZST 2010 ],INFO ,[main],com.cisco.nm.rmeng.dcma.configmanager.DcmaBaselineTemplateMigrator,doMigration,225,Baseline Migration not needed
    Also, the only entry in the job directory ..\CSCOpx\files\rme\jobs\ArchiveMgmt\8628 is the job.obj.
    Given the error that is in the log file, perhaps this is no surprise.
    Regards
    Jeff

  • LMS 4.1 - Archive Mngt - excluded Commands

    Dear all,
    In previous LMS version, we could edit a list of commands that have to be excluded while comparing configuration.
    To do this select
    Resource Manager Essentials > Admin > Config Mgmt > Archive Mgmt> Exclude Commands
    How to do in LMS 4.1? (required in order to exclude "ntp clock-period")
    Thanks

    Admin > Collection Settings > Config > Config Compare Exclude Commands Configuration
    There is alse the legacy menu, the thingy next to the yellow star on the top right of the screen
    Cheers,
    Michel

Maybe you are looking for