Device Credential Verification Job

I have a device credential verification job which runs one per week.
Every now and again the job hangs and no matter what I do I can't stop the job to delete it. I can see the job in the job list and I can select it and choose STOP, howeverm after that the job stick in a "Stop Initiated" state and never changes. I've tried rebooting the server and this doesn't affect the job state or my inability to delete the job.
I can successfully create another Device Credential Verification Job and these run fine for several weeks.
Two questions.
1. Any idea's what's causing the job to hang
2. How can I delete the jobs that are stuck in a "stop initiating" state
Thanks,

It may be that you will need to get TAC involved to clean the job out of the database directly.  However, you can try the following first.  Run the "pdshow" command, and check for a daemon named the same as the job ID.  If you see it, run:
pdreg -u JOB_ID
That should unregister the job daemon.  Then see if you can stop and delete the job.

Similar Messages

  • Sending Ciscowrks device credential Verification Job alters the device ARP table.

    Hi:
    I send a Device credential verification Job to two different devices  , a Cisco 3750 and a blade switch WS-CBS3120. I  configured SNMP write access to the switches. The SNMP write access in either SNMP v1 or SNMP V3 , tried both.
    The job is send from the Ciscoworks server.
    Once the job has completed, I do a show ip arp on the device and find a new entry with the IP address of the Ciscoworks  Server and the mac-address of the L2 next hop.
    We would not have  noticed this behavior had it not been that in the case that the  switch  next hop is an HSRP vlan on a nexus , the ARP entry entered into the switch is incorrect, and from then on the switch loses connection to Ciscoworks.
    The Mac-address that is entered by Ciscoworks , in the case of nexus is a statice mac defined on the Nexus for the Vlan in question , but it is NOT the HSRP default gateway MAC address. Therefore we lose connection between the switch and Ciscoworks. One has to manually clear the ARP table inorder to again reach the Ciscoworks.
    Questions:
    1. Why does Ciscoworks  insist on changing the ARP table?
    2. Is this ARP entry aged out or is it permeant as would an ARP entry which is entered through CLI  be  permeant ?   
    3. In the case of the Nexus connection, this ARP entry does not allow Ciscoworks and the device to communicate. This is not productive!
    Has any one come across this situation ? Any known fixes, workarround? I was not able to find a word about this on Cisco's site.
    Our Ciscoworks is at the following levels:
    CW Common services    3.3.0
    LMS portal                    1.2.0
    CW Assistent                1.2.0
    RME                             4.3.1
    Device fault manager      3.2.0
    IPM                              4.2.1
    Cisco View                    6.1.9
    campus Manager            5.2.1
    thanks   for any help
    Mickey

    CiscoWorks does not change the ARP table, at least not overtly.  A credential verification job will do the following things depending on what protocols are selected to test:
    SNMP RO : Fetches sysLocation.0
    SNMP RW : Sets sysLocation.0 to the value currently stored in sysLocation.0
    Telnet : Logs in using DCR username and password
    SSH : Logs in using DCR username and password
    Enable : Enters enable mode and verifies privilege level 15
    If one of these things are causing the ARP table to change, then there is something fishy in the device or network configuration.  I've never heard of such behavior relating to CiscoWorks before.

  • Device Credential Verification Job Error

                  When starting Device Credential Verification Job, we have following error:
    CDA0114: Operation failed while connecting to JRM. Make sure jrm and/or CTMJrmWrapper services are up and running.
    In cda.log, there is error:
    com.cisco.nm.xms.ctm.common.CTMException: URN_NOT_FOUND : urn "JRM" : Not found !!
    How could we proceed to solve these problems?
    We have LMS3.2.1 installed on Windows 2003 Standard Edition server.
    Please find attached log files.

    Hello,
    I have a similar problem. I have configured a snmp v3 user using SHA to authentication an DES for private access.
    We use RME 5.0.1 and when we try to run a CDA it doesn`t work reporting "Error performing SNMP operation".
    In the log of the CDA job, we can see:
    [ lun nov 26  16:46:06 CET 2012 ],INFO ,[Thread-6],com.cisco.nm.rmeng.inventory.cda.job.DoCDAonDevice,updateCdaStatus,1784,Executing sqlStmt update DM_Credential_Error_Status set Cred_Status= 8 ,Cred_Status_Descr='Error performing SNMP operation.',Update_At='1353944766699' where NetworkElementID = 3685 and Cred_Type = 3
    How can I use snmp v3 with RME 5.0.1?
    Thanks.

  • RME Device Credential Verification Report

    I have a Device Credential Verification Job which runs each week. It has run fine for the last few months, however, this week the job started but didn't finish and appears to have hung.
    The job usually takes around 25mins to run (circa 350 devices) but this week it was still running after 19 hours. Eventually I tried to stop the job but it is now stuck in a state of "Stop Initiating".
    I've stopped/started the services and evenutallty even rebooted server but this particular job remains stuck in "Stop Initiating" state.
    Is there any way to fix this?

    Hi Joe,
    LMS3.2.
    The job is validating SNMP/v2c Read & Write, Telnet and Telnet Enable.

  • Device Credential report

    Hi all,
    I am running device credential reports to see if SNMPV2/V3 is ok and some devices are coming back wrong credentials/credentials not verified.
    I'm looking at the date and some are from last year Dec 1 2008 and I just applied changes to some devices last night. I also verified on the device that the correct credentials are there.
    Please help.

    Are you running this report ?
    RME > Reports > Report Generator > Device Credential : Verification Report
    RME Reports from the Report Generator are always based on information collected by a job and stored in the database. If this job is not configured to run periodically it is truely possible that you have outdated data in the report.
    Go to RME > Devices > Device Management > Device Credential Verification Job and setup a job to check the credentials immediately, once or periodically;
    At least if you let it run immediately your report should contain actual and correct data.

  • LMS 4.1 Credential Verification Report

    Hi,
    when running Credential Verification Report, I get following notification: "None of the devices have credential verification data".
    I have made different Default Device Credential sets that I'm using when I add devices to LMS. I been looking at the forums here, but I could not see wether this is bug in LMS 4.1 or if I have to do this a different way?
    Regards,

    I'd suggest doublechecking your work by following the "Update the credentials" procedure on page 8 of this handy intro guide posted in the documents section of this forum.
    Hope this helps.

  • Error message when trying to run check device credential job

    unable to run check device credintial job. says to check cda.log:

    You're seeing CSCte49301.
    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.

  • Pre-qualification Test Suites for Device Driver Verification

    Pre-qualification test suites for verification of network and storage device drivers on Solaris(TM) 7 (Intel Platform Edition) are now available. These test suites are prototypes of test suites we plan to make available later this year. We are making the prototypes available for download
    because IHVs (Independent Hardware Vendors) and third-party developers have told us these tests are useful in assessing the readiness of their drivers. Please note that these prototype test suites are unsupported. We welcome your comments, which can be submitted by e-mail to
    [email protected]
    The test suites (NETTests for network drivers, SUNWprtst for storage drivers) are on the Developers Tools page (http://soldc.sun.com/developer/support/driver/tools/). If you're a
    registered user of the Solaris Developers Connection, log on and go straight to this page, then choose the network or storage test suite to download. If you haven't registered yet, go to
    http://soldc.sun.com to register (it's quick and it's free). You'll find links to the test suites under "What's New" on this same page.

    Pre-qualification test suites for verification of network and storage device drivers on Solaris(TM) 7 (Intel Platform Edition) are now available. These test suites are prototypes of test suites we plan to make available later this year. We are making the prototypes available for download
    because IHVs (Independent Hardware Vendors) and third-party developers have told us these tests are useful in assessing the readiness of their drivers. Please note that these prototype test suites are unsupported. We welcome your comments, which can be submitted by e-mail to
    [email protected].
    The test suites (NETTests for network drivers, SUNWprtst for storage drivers) are on the Developers Tools page (http://soldc.sun.com/developer/support/driver/tools/). If you're a
    registered user of the Solaris Developers Connection, log on and go straight to this page, then choose the network or storage test suite to download. If you haven't registered yet, go to
    http://soldc.sun.com to register (it's quick and it's free). You'll find links to the test suites under "What's New" on this same page.

  • Device credential problem?

    I Have LMS 3.1 under Solaris 9.
    I have a switch 2950, your communities RO and RW, Telnet and enable Telnet are OK. But SSH and enable SSH are not enabled because SSH is no supported feature for this device.
    Why I get in console device a problem authentication failure for SNMP? if my credentials are OK.
    l"
    Feb 27 14:01:14 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Feb 27 14:01:20 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Feb 28 10:01:12 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Feb 28 10:01:18 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Feb 28 14:00:54 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Feb 28 14:01:00 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Mar  1 10:01:03 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Mar  1 10:01:09 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Mar  1 10:09:52 BsAs: %SYS-5-CONFIG_I: Configured from console by vty1 (192.168.16.154)
    Mar  1 14:01:04 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Mar  1 14:01:10 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Mar  2 10:01:13 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Mar  2 10:01:19 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Mar  2 14:01:11 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Mar  2 14:01:17 BsAs: %SNMP-3-AUTHFAIL: Authentication failure for SNMP req from host 10.24.0.43
    Please, How can I eliminate this error message?
    Thanks very much in advance!!

    find out who is responsible for server with IP 10.24.0.43 and look for an application that snmp polls your device.
    Just a suggestions...as from the timeline of the failure, the server is LMS and the application is UTMajorAcquisition (default jobs at 10:00 and 14:00). Thus it could be a problem with snmp indexing to get vlan information.
    In former versions of LMS when seeing this failure, you had to verify that the following parameters had this values:
    NMSROOT/campus/etc/cwsi/AniServer.properties
    UTGetSuspendedVlans=0
    Run a new User Tracking Acquisition (from Campus Manager > Home) and see if the problem has gone.
    if this does not help also make sure you have got the following settings:
    NMSROOT/campus/etc/cwsi/ANIServer.properties
    UTGetVlansOnDownPorts=0
    NMSROOT/campus/etc/cwsi/ut.properties
    UTGetVlansOnDownPorts=0
    UTGetVlansOnUserPortsIOS=1
    Always make backup of the file before changing any value !

  • I Cloud approval from other device or verification code?

    I just upgraded to IOS8 on iPad 3 and iPhone 6.  For the I cloud set-up it is asking for an approval from another device or entering a verification code. 
    1.  How to approve from other device?  I have an iMac as well.  OR
    2.  If you enter code the message is a verification code will be sent to a phone number (which is my house phone....does not receive texts).
    What to do?

    Hi Brad0266,
    Thank you for using Apple Support Communities.
    From your post it appears that you have enabled two-step verifcation for your Apple ID, which is why it is prompting you to enter in a verification code from a device that you set up.  Take a look at the support article linked to below to learn more about two-step verification.
    Frequently asked questions about two-step verification for Apple ID
    Cheers,
    Alex H.

  • Cisco Works Enable username credential missing

    I have tried to deploy a configuration out as well as running a Device Credential Verification Job and they both fail because of "Enable username credential missing." I can not seem to pin point the problems because there is no place to add this, also our switches do not asking for a username while going into enable mode. Would TACACS+ have anything to do with this?

    Apologies for resurrecting this old thread... I have found myself in a similar situation. And I have run a wireshark capture to review the entire telnet session. Obviously I am using generic passwords here, but this what I get when I follow the TCP stream. And yes, I did indicate that this is an IOS device, not CatOS (which is why I'm confused about that "set" command).
    Username: ciscoworks
    Password: sample_password
    Switch6513>
    Switch6513>
    Switch6513>
    Switch6513>
    Switch6513>_tune_
    Switch6513>
    Switch6513> set length 0
    Switch6513>
    Switch6513>
    Switch6513> enable
    Password: sample_password
    Switch6513#
    Switch6513#
    Switch6513#
    Switch6513# _tune_
    Switch6513#
    Switch6513#
    Switch6513# _tune_
    Switch6513#
    Switch6513#
    Switch6513# enable
    Switch6513#
    Switch6513#
    Switch6513# _tune_
    Switch6513#
    Switch6513#
    And Ciscoworks still reports "Enable username credential missing" even though the switch is obviously in enabled state.
    Needless to say I'm trying to push the upgrade to NCS, but it's kinda difficult when the existing installed software isn't working as advertised.

  • LMS 4.0 Default Credential Set Policy

    Hello,
    I would like to assign to all hosts in the subnet 192.168.252.0/24 and 192.168.254.0/24 a dedicated credential set named set01. I created a default credential set policy configuration
    IPRange#192.168.254.*#Set1
    IPRange#192.168.252.*#Set1
    right after the discovery process i run a device credential verification job. where only the read community is OK. So I assume the policy isn't working. Is there any prerequisites for deploying credential policy sets?
    thanks in advanced
    Alex

    Credential sets are only applied to devices when they are added to DCR.  If they were already in DCR, you have to go to Inventory > Add / Import / Manage Devices to forcibly change the credentials to those in the credential set.

  • Problems seeing a device in Prime LAN

    I have been going through the documentation for Prime LAN and havent been able to see what I am not doing right.
    I can import/discover a device and get the message on the screen that 1 device has been found and imported into DCR.
    I cant see the device anywhere in Cisco Prime.  To keep things simple, I have put a test device on the same subnet as the VM running Prime LAN.
    I had used a version of Ciscoworks several years ago and didnt have this much problem getting it to work.
    I have put in a simple snmp v2 ro community name.  In Dashboards, Device Status, I can see a 1 under Success in Device Discovery Status.  If I click on the 1, I do get a screen that shows me the device that it found.  That is the only place that I can see the device.
    Suggestions ?

    Thanks for the document.  I must be missing something.  I deleted the device that Prime LAN had discovered and reran the discovery process.  I was able to rediscover the device.  It got a popup that I needed to run a device credential verification job.
    That is where I run into the problem.  I can assign the credential set I want to be used on the router.  I am prompted to run a Device Credentials Verification job/process.  When I go to do that process, I cannot see the device that I have discovered to be able to run the job against to verify the credentials.
    At this point, this is an isolated system.  I have the "test" router that it is initially talking to on the same subnet as the Prime LAN server is on, so that takes care of a router or firewall as being part of the problem.  I can ping from the router to Prime LAN and vice versa.
    Suggestions ?

  • LMS 4.1 Energywise Endpoint issue

    I have 10 switches as members of the same, local, energywise domain.  When I perform a show energywise neighbors on any of the given switches, they all appear.  If i perform show energywise children on a given switch, i see the children of that switch.
    When i attempt to "Collect Endpoints" the collection is a success, but my 10 switches only show 2 endpoints, which are 2 of the 10 switches that are configured as a stack.  When i remove that stacked 3750G from the energywise domain, it still only shows 2 endpoints, but now they are 2 other switches that are configured as a stack.
    Is it that LMS 4.1 has difficulty detecting endpoints in a group where Stack switches are used, or am I missing something in my config?  LMS 4.1 says it "knows the secrets" and has not had a single Energywise query error out, so i can only assume its gathering all the information its supposed to be, but somehow it never detects any of my actual endpoints, only the 1st set of stacked switches in the group.

    Hello,
    Are you sure that the LMS support the config collection on these devices ?
    Check on this link :
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/device_support/table/lms41sdt.html
    If yes, it means that you have a problem for the file transfer... I would suggest to debug like this :
    1) Check the credentials (Inventory->Job Browser->Device Credential Verification Jobs, then create a new one)
    2) Is it possible to do a tftp from the device to the LMS ? (If the config is done by tftp)
         Create a tmp file on /tftpboot on LMS
         Copy the startup or running file from the device to the LMS with the name of your tmp file (it is not allowed to create a file on the LMS with TFTP)
    3) Do a sniffing of the traffic between the LMS and the device in order to see what happen
         Go on :1741/cwhp/PacketCapture.do">http://:1741/cwhp/PacketCapture.do
    BR

  • DFM Discovery issue

    We have install Ciscoworks LMS 3.2 on windows server 2003 enterprise edition.
    DFM version is 3.2.0.
    While rediscovering devices most of the switches are in Questioned SNMP timeout. If I run device credential verification job for SNMP from RME>Devices>Device Management job executs successfully.
    We are using SNMP V3.
    Need assistance for the same.

    Hi,
    Be aware that DFM do not support all the privacy algorithms for SNMP V3.
    DFM supports the following:
    For authentication: Sha, MD5
    For privacy DES and AES128
    The following privacy algorithms are not supported:
    3DES, AES192, and AES256
    You can double check this on the User Guide:
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_device_fault_manager/3.2/user/guide/useDevMg.html#wp1483766
    Hope this helps.
    Andres

Maybe you are looking for