Config archive failed for devices no longer on DCR

RME reported 30 devices failed config archive but this devices are already removed from DCR but RME keep reporting this devices. how I can clean up thiese devices from RME?
Thanks

You can contact TAC, and they can give you the procedure to surgically remove these device records from the RME database.

Similar Messages

  • ISE Alarm (WARNING): Dynamic Authorization Failed for Device

    Hi all,
    I am posting this discussion as previous posts that I have found in this forum have never been resolved or the resolution is not applicable to me.
    I am using ISE 1.1.1.268 and WLC 7.2.111.3 and NAC agent version 4.9.1.6 on Windows 7 Client machines.
    About once a day i get the error "ISE Alarm (WARNING): Dynamic Authorization Failed for Device".
    The device it is reffering to is my NAD, a WLC 5508 running 7.2.111.3
    I have looked at the logs and I cannot see anything in the logs which correcponds to this message so that I can troubleshoot further. Maybe I can if I am enabling the correct logging level on the correct ISE component.
    Can someone suggest the components and the logging level that I should set to get some more detail about this error?
    At the moment, I have only set debug logging on Active Directory. I have TRACE logging set on Posture, Runtime AAA & prrt-JNI.
    I do not want to enable too much debug logs, so I was wondering whether anyone can help with a specific element that I should be debugging.
    I thought debugging the posture element would be enough but when I look at the logs there is nothing there that relates to this message.
    Can anyone help?
    thanks
    Mario

    Firstly, I wouldn't run a production deployment of ISE on 1.1.1.... 1.1.3 Patch 1 or 1.1.4 is the way to go.
    Secondly, this error happen a lot, especially with Wireless, and it's not worth worrying about.  I've had a couple of TAC cases opened for this and some similar errors, generally they're caused by a Client going to sleep, leaving the coverage area or otherwise leaving the WLC while ISE is trying to do something with it.
    Only worry if you actually have a Client-impacting problem, which by the sounds of it, you don't.

  • LMS 4: VLAN config fetch failing for all devices

    LMS 4.0.1, standalone on W2K8 R2, new install
    Vlan config fetch is failing for all devices.  If I attempt to put a vlan.dat file in tftpboot and then manually copy a vlan.dat file from a device, the following is returned:
    TFTP: error code 2 received - 16739
    %Error opening tftp://server_name/vlan.dat (Permission denied)
    The Windows application logs ont the server log this:
    Log Name:      Application
    Source:        CRMtftp
    Date:          6/15/2011 2:07:49 PM
    Event ID:      3
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      server_name
    Description:
    GetEffectiveRightsFromAcl failed: Overlapped I/O operation is in progress.
    (997)
    I tried restarting crmtftp, but no luck.  Any ideas what may be causing this?
    -Jeff

    I have the same issue with a freshly installed 4.2 version now:
    Log Name:      Application
    Source:        CRMtftp
    Date:          2/24/2012 12:30:50 PM
    Event ID:      3
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      srvwienlms.nts.local
    Description:
    GetNamedSecurityInfo failed failed: The operation completed successfully.
    (0)
    I will also open a TAC case, lets see if we still have to stick with a3.x TFTP binary...
    br.herwig

  • Cisco VG248 config archive fails

    I beleive in the past these devices could not be managed bij RME config management, but now it says in the supported device table:
    The following features are supported:
    Network Topology Layer 2 Services
    Fault Management
    Inventory Collection
    Configuration Deploy Protocols: TELNET, SSH, TFTP, RCP
    Configuration Fetch Protocols: TELNET, SSH, TFTP, RCP
    The password and enable pasword are correct and simply work when I try a telnet from the server.
    The gui is not CLI but menu driven.
    RME just says:
    TELNET: Failed to establish TELNET connection to 10.1.1.7 - Cause: Authentication failed on device 3 times. PRIMARY-RUNNING config Fetch Operation failed for TFTP. Could not detect SSH protocols running on the device.
    What can be wrong?
    Cheers,
    Michel

    Hi Michel,
    Thanks for the screenshot. I found that you now have customized prompts in tacacspropmt.ini file.
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : Username: *
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : username: *
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : login: *
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : Username:*
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : username:*
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : login:*
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : username:*
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for user prompt : Username:*
    [ Fri Aug 26  11:30:26 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Checking for password prompt : Password: *
    and look like RME is able to login to device as well now :-
    [ Fri Aug 26  11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,State traversal for telnet login:
    [ Fri Aug 26  11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Connected
    [ Fri Aug 26  11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Verify
    [ Fri Aug 26  11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,Success
    [ Fri Aug 26  11:29:11 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,debug,31,login succeeded
    Kindly run the credentials verification job and let me know the results --> Is the device still failing for the telnet and enable password ?
    Also navigate to CSCOpx\objects\cmf\data and uncomment the following on file cmdsvc.properties like this :-
    InitialTransportTimeout=50000
    TransportTimeout=90000
    TuneSleepMillis=3000
    DelayAfterConnect=1000
    LMS was not able to login to device successfully yet or it could be timeout issue. After this LMS try to get the config of the device using SNMP and tftp, but look like tftp is blocked in network too, See this :-
    [ Fri Aug 26  11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator,fetchConfig,170,Initialized SNMP
    [ Fri Aug 26  11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.LibCommon.snmp.ConfigCopyMib,copyFromRunning,119,FileName= 20110826113104185-10.13.192.9.cfg tftpDir =  User =  password =  serverAddr = 10.1.3.156
    [ Fri Aug 26  11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.LibCommon.snmp.ConfigCopyMib,copyFromRunning,130,Cannot create variable binding list com.cisco.nm.lib.snmp.lib.SnmpException: SnmpResponseGenErr on 10.13.192.9 while performing SnmpSet at index = 0
    [ Fri Aug 26  11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator,fetchConfig,182,Fetch completed
    [ Fri Aug 26  11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator,fetchConfig,190,PRIMARY-RUNNING config Fetch Operation failed
    [ Fri Aug 26  11:31:04 CEST 2011 ],DEBUG,[Thread-956],com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator,fetchConfig,196,PRIMARY-RUNNING config Fetch Operation failed for TFTP. java.lang.Exception: PRIMARY-RUNNING config Fetch Operation failed for TFTP.
        at com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator.fetchConfig(GenericTftpOperator.java:192)
        at com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericTftpOperator.fetchConfig(GenericTftpOperator.java:93)
        at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.SimpleFetchOperation.performOperation(SimpleFetchOperation.java:61)
        at com.cisco.nm.xms.xdi.pkgs.LibDcma.persistor.ConfigOperation.doConfigOperation(ConfigOperation.java:111)
        at com.cisco.nm.xms.xdi.pkgs.SharedDcmaGeneric.transport.GenericConfigOperator.fetchConfig(GenericConfigOperator.java:72)
        at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.updateArchiveForDevice(ConfigManager.java:1317)
        at com.cisco.nm.rmeng.dcma.configmanager.ConfigManager.performCollection(ConfigManager.java:3307)
        at com.cisco.nm.rmeng.dcma.configmanager.CfgUpdateThread.run(CfgUpdateThread.java:27)
    So, in summary, kindly edit the cmdsvc.properties file and make the changes as I suggested . Also let me know the results of the credentials verification job and run the packet capture while running the credentials verification job.
    Many Thanks,
    Gaganjeet

  • Sync Archive fails for CRSs on LMS 3.1

    Hi, I've been trying to collect the configuration of some CRS-1 4-slot but it keeps on failing. These are the only devices I'm missing (out of 2,000). I've tried to tweak the timeout values but it makes no difference. The actual values are set to:
         SNMP Retry = 6
         SNMP Timeout = 90 sec
         Telnet Timeout = 120 sec
         TFTP Timeout = 60 sec
    The protocols I'm using to retrieve the configs are SSH, Telnet, and TFTP. Telnet is disabled on this devices, they use SSH v2 instead. What I get from the job details is:
    *** Device Details for 9R_MCO_NEXTENGO ***
    Protocol ==> Unknown / Not Applicable
    Selected Protocols with order ==> SSH,Telnet,TFTP
    Execution Result:
    CM00139 Could not archive config Cause: Action: Verify that device is managed and credentials are correct. Increase timeout value, if required.
    They are managed by RME, indeed and it has been able to collect their inventory. This CW is installed on Solaris 9. If I try to SSH from the console it prompts me for a password, but if I type in CW server's account password it won't log me in. Then I need to specify my username and I'm able to get access.
         # ssh 10.255.0.41 -l CISWORKS
    Does this looks like an SSH issue? Then it should be able to collect the configs by TFTP. Or are CRSs not fully supported on LMS 3.1? This devices are running IOS XR 3.6.2.
    Thanks in advance.

    This sounds to me like the credentials are misconfigured in DCR.  Go to Common Services > Device and Credentials > Device Management, and re-enter the username and password for this device.  Then see if you can archive the configuration.  The CRS-1 4-slot chassis is supported in RME 4.2.

  • SP Products Config Wizard fails for Socket Error Connection Refused - New Azure Setup (firewalls turned off)

    Hi all,
    I'm using this guide: "Step-by-Step: Build a FREE SharePoint 2013 Dev/Test Lab in the Cloud with Windows Azure Infrastructure Services" by Keith Mayer 15 Jul 2013 6:30 AM over on TechNet.
    And I'm currently in "Exercise 5: Configure SharePoint Server 2013 in a Windows Azure VM" steps 16/17.
    When I try to create a new server farm following those instructions, the process fails.
    The dialog window states:
    "Configuring SharePoint Products"
    "Performing configuration task 3 of 10" <- gets stuck here for a while and then I get the error below: 
    The error from the PSCDiagnostics log is:
    Trying to see if port 14387 is free on machine [my sp server]. Min port we will try is 1024, Max port we will try is 49151
    05/14/2014 16:43:26 1 INF A SocketException was thrown with SocketError ConnectionRefused
    05/14/2014 16:43:26 1 INF Connect has been refused for port 14387, so we will consider this a free port
    05/14/2014 16:43:26 1 INF Have not found a free port yet. Number of tries is 1. Min port we will try is 1024, Max port we will try is 49151
    05/14/2014 16:43:26 1 INF Adding port 14387 to the exclusion list so it is not chosen again during this run
    [snip]
    05/14/2014 16:48:22 9 ERR Task configdb has failed with an unknown exception
    05/14/2014 16:48:22 9 ERR Exception: System.Data.SqlClient.SqlException (0x80131904): A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.) ---> System.ComponentModel.Win32Exception (0x80004005): The semaphore timeout period has expired
    I've turned Windows firewall off on the SP Server, SQL Server and the AD Server (temporarily of course) and I've given user mydomain\sp_farm local and domain administrative rights as well as full rights within the SQL db.
    I can ping from/to the SharePoint/SQL servers and get a response using the host name for each (the internal IP's 10.0.0.5/6 respond).  If I use the DNS server names, the pings fail.
    However, after the SharePoint wizard fails, I can see on the SQL server that db SharePoint_Config (default name from SP wizard) is created.  So it looks like the SP wizard can connect because the db is being created.
    Is this a timeout issue even though the log file shows "SocketError ConnectionRefused"?
    Any ideas on how I can resolve this error?
    Thanks.

    Hi Gary, 
    For this issue, I'm trying to involve someone familiar with this topic to further look at it. 
    There might me some time delay. Thank you for your understanding.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Unmount failed for device

    I want to erase my internal HD to perform a clean Lion install but i get the message that the drive cannot be unmounted? Why not.
    I've booted from an external HD with a SuperDuper back up.

    Got it: just a simple restart of the system on the external took away the 'can't unmount' message about the internal HD.

  • Config archive of Cisco 4404/4402 WLC devices

    Hi,
    I am currently having an issue backing up WLC devices in CiscoWorks LMS 3.2. i can see that from an inventory perspective they are discovered correctly. I have tested the credentials on the CLI and that works fine, but when doing a archive collection from the ciscoworks application it fails, stating that it is a timeout issue.
    I have noticed that when trying to connect via the CLI using SSH example below, it does not just prompt for a password, it prompts for the username again, i am not sure if this is the issue
    ssh -l test 10.1.2.3
    Any assistance will be much appreciated
    Kind Regards
    James

    Hi
    telnet output on port 22:
    Trying *.*.*.*
    Connected to *.*.*.*
    Escape character is '^]'.
    SSH-2.0-OpenSSH_4.0
    Protocol mismatch.
    Connection to *.*.*.* closed by foreign host.
    Failed info in job output:
    CM0151 PRIMARY RUNNING Config fetch failed for hostname Cause: fig from device: java.net.SocketTimeoutException: Read timed out Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.
    dcmaservice.log  output:
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-5],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,triggerConfigFetch,52,#### Start of Sweep Tue Apr 13 10:46:48 BST 201
    0 ####
    [ Tue Apr 13  10:46:48 BST 2010 ],WARN ,[Thread-6033],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getResultFromQuery,3315,SQLException occurred as connection closed. Re-connecting
    to DB...
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,769,Inside RMEDeviceContext's getCmdSvc ....
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,774,Protocol and Platforms passed = SSH , RME_WLC
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,786,Iam inside ssh ....
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,787,Initial time_out : 0
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,792,Computed time_out : 60
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,800,After computing time_out : 60
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,819,inside getSshCmdSvc with timeout : 60000
    [ Tue Apr 13  10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshProtocols,872,Inside getsshprotocols with time out : 60000
    [ Tue Apr 13  10:46:54 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,826,SSH2 is running
    [ Tue Apr 13  10:47:00 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,error,19,Warning: Received USERAUTH_SUCCESS in response to 'none' authen
    tication request
    [ Tue Apr 13  10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,342,SNMP initialization completed
    [ Tue Apr 13  10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,349,Current Running image version:NoSuchIns
    tance
    [ Tue Apr 13  10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,351,Using the latest command as image veris
    on is greater than 5.2
    [ Tue Apr 13  10:48:25 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,error,19,IOException received during block() of Channel[UInt32[ 0 ]:UInt
    32[ 0 ]]
    [ Tue Apr 13  10:48:26 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,678,PRIMARY RUNNING Config fetch Failed for
    hostname
    [ Tue Apr 13  10:48:26 BST 2010 ],INFO ,[Thread-1],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,run,99,#### End of Sweep Tue Apr 13 10:48:26 BST 2010 ####
    SNOOP output:
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Syn Seq=1825561549 Len=0 Win=49640 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720941 Seq=1825561550 Len=0 Win=50040
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720961 Seq=1825561550 Len=0 Win=50040
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Fin Ack=669720961 Seq=1825561550 Len=0 Win=50040
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Syn Seq=2323886065 Len=0 Win=32850 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720962 Seq=1825561551 Len=0 Win=50040
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581283 Seq=2323886066 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581303 Seq=2323886066 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581303 Seq=2323886066 Len=15 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581303 Seq=2323886081 Len=248 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581943 Seq=2323886329 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581943 Seq=2323886329 Len=144 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582407 Seq=2323886473 Len=16 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582407 Seq=2323886489 Len=52 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582459 Seq=2323886541 Len=68 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582495 Seq=2323886609 Len=60 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582547 Seq=2323886669 Len=76 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582583 Seq=2323886745 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673582707 Seq=2323886789 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582775 Seq=2323886789 Len=52 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673582879 Seq=2323886841 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582879 Seq=2323886841 Len=52 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582931 Seq=2323886893 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582931 Seq=2323886937 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583039 Seq=2323886981 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583083 Seq=2323887025 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583127 Seq=2323887069 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583171 Seq=2323887113 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583215 Seq=2323887157 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583259 Seq=2323887201 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583303 Seq=2323887245 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583347 Seq=2323887289 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583407 Seq=2323887333 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583407 Seq=2323887333 Len=60 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583467 Seq=2323887393 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583535 Seq=2323887437 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583535 Seq=2323887437 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583595 Seq=2323887481 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583595 Seq=2323887481 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583639 Seq=2323887525 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583707 Seq=2323887569 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583707 Seq=2323887569 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583775 Seq=2323887613 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583843 Seq=2323887657 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583887 Seq=2323887701 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583931 Seq=2323887745 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583975 Seq=2323887789 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584019 Seq=2323887833 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584063 Seq=2323887877 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584107 Seq=2323887921 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584151 Seq=2323887965 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584219 Seq=2323888009 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584219 Seq=2323888009 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584287 Seq=2323888053 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584287 Seq=2323888053 Len=52 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584339 Seq=2323888105 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584415 Seq=2323888149 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584415 Seq=2323888149 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584483 Seq=2323888193 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584483 Seq=2323888193 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584527 Seq=2323888237 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584587 Seq=2323888281 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584587 Seq=2323888281 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584647 Seq=2323888325 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584707 Seq=2323888369 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584751 Seq=2323888413 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584795 Seq=2323888457 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584839 Seq=2323888501 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584883 Seq=2323888545 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584927 Seq=2323888589 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584971 Seq=2323888633 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585015 Seq=2323888677 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585075 Seq=2323888721 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE UDP D=161 S=53008 LEN=77
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585075 Seq=2323888721 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585135 Seq=2323888765 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585135 Seq=2323888765 Len=68 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585203 Seq=2323888833 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585735 Seq=2323888877 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585735 Seq=2323888877 Len=44 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585735 Seq=2323888921 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673587523 Seq=2323888921 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673587523 Seq=2323888921 Len=36 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673587523 Seq=2323888957 Len=128 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673587524 Seq=2323889085 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Fin Ack=673587524 Seq=2323889085 Len=0 Win=33072 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Syn Seq=3874994962 Len=0 Win=49640 Options=
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Ack=754769594 Seq=3874994963 Len=0 Win=50040
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Fin Ack=754769594 Seq=3874994963 Len=0 Win=50040
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Rst Seq=3874994964 Len=0 Win=50040
    LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Rst Seq=3874994964 Len=0 Win=0
    Kind Regards
    James

  • Error Message in config Archive in RME in LMS 4.2

                      I got the below error message in the config archive in the LMS 4.2.
    CM0056 Config fetch failed for 10.0.0.10  Cause: CM0204 Could not create DeviceContext for 797 Cause: CM0202 Could not access 10.0.0.10 via SNMP. Action: Check the Read Community string Action: Check if required device packages are available. Action: Check if protocol is supported by device and required device package is installed.
    Switch model type is 3560 and 2960
    Please tell me the reason for this issue.

    Are you usig only TFTP option to archive configuration. Try to use the telnet/ssh. TFTP as a protocol set for config archive.
    Check the Credential verificatio job to see if the crendentials are configured correctly.
    -Thanks

  • LMS 3.2 - RME 4.3.1 Sync archive fails

    Hi,
    Sync archive fails for some of my devices.
    This is the message :
    *** Device Details for .... ***
    Protocol ==> Unknown / Not Applicable
    Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS
    Execution Result:
    CM00139 Could not archive config Cause: Action: Verify that device is managed and credentials are correct. Increase timeout value, if required.
    Check device credential is OK (Telnet + SNMP V2)
    This device is Cisco Systems WS-C6009.Cisco Catalyst Operating System Software, Version 7.4(3). (sysObjectID : enterprises.9.5.39)
    I have modified the "Maximum time to wait for Job Results per device (seconds):" to 240.
    What could be wrong?
    Thanks in advance

    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

  • Config Archive Failure

    This image shows that I have Telnet, SSH, TFTP and HTTPS configured for  Config Fetch. What am I missing?
    Thanks Joseph!
    I don't know why, but nearly ALL of my Config Archive VLAN is failing. I am  receiving the following:
    TELNET: Failed to establish TELNET connection to xxx.xxx.xxx.xxx - Cause:   Connection refused. Command failed  VLAN Config fetch is not supported using  RCP.   VLAN Config fetch is not supported using TFTP.
    The above switch is using SSH - not Telnet, but it doesn't try???
    The other error is:
    Command failed  Could not detect SSH protocols running on the device     VLAN  Config fetch is not supported using RCP.   VLAN Config fetch is not supported  using TFTP.
    On this one, it should be using Telnet as that is what is supported on this  particular switch.
    I have verified the credentials are set up correctly for both of these.
    Also, this isn't isolated - it's happening on 293 devices. Only 2 are  successful.
    Any help would be GREATLY appreciated! I am running LMS 3.2

    The following is what I see in the logs:
    ],ERROR,[Thread-1926],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1355,VLAN RUNNING Config fetch Failed for csw-a1xc-201-004
    [ Fri Oct 08  06:27:18 MDT 2010 ],DEBUG,[Thread-1926],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,1361,Message : Command failedSSH: Failed to establish SSH connection to x.x.x.x -
    Cause: Authentication failed on device 3 times.
    VLAN Config fetch is not supported using TFTP.
    Please ensure that you have the credentials corrected in the DCR under Common Services --> Device and Credentials --> Devices Management --> Select all the devices in question, edit credentials.
    1. Ensure the primary enable username and password is correct and populated.
    2. Ensure you are using the correct SNMP RO/RW community string and must be populated.
    3. Ensure that all firewall rules allow traffic to and from LMS and devices. Check port 69 UDP and high ports number are allowed.
    4. If this is a multi-home system with two nic cards, go to RME ---> Administration --> System Preferences --> RME Device Attribute --> Add Natted RME IP Address
    Afterwards, rerun the device credential verification to test for telnet, ssh, SNMP RO and RW and ensure it passes. Then do a sync archive and let me know the results.

  • Call manager and rme config archive report

    Hi,
    I know that rme does not support the call manager for config archive. It is clear.
    The RME home page show config archive status for failed devices and there are some devices which are not supported by RME config archive.
    I've set this devices to suspended state in RME but config archiv is trying with this devices also.
    This is a financial costumer and the local Financial supervisory authority would like to see all devices config is saving successfully.
    How can i exclude the call manager and similar devices from config archiv process and status reports?
    Regards,

    Hi,
    I would like to qoute from RME help.
    Working With Suspended Devices
    Suspended device state cannot participate in any RME application flows but all historical data pertaining to the device will continue to be maintained by RME.
    Nevertheless the RME is trying to fetch the config from suspended devices!!!
    What is the truth in this thing?
    Regards,

  • Config Fetch Failed

    The error message below is from a device that I am trying to sync a configuration, device is using TACACS:
    RUNNING
    CM0151 PRIMARY RUNNING config fetch failed for ROUTER Cause: TELNET: Failed to establish a Telnet connection to
    X.X.X.X Cause connection refused.
    SSH: Same message as aboove except authentication failed on device 3 times.
    ACTION: Check if protocal is supported and required on device package is installed.

    The error about authentication is usually correct.  Go to Common Services > Device and Credentials > Device Management, select the device in question, then export the credentials.  Look at the CSV export, and take the username and password, and try to SSH to the device from the LMS server.  Verify you can login and get into enable mode using the same credentials in DCR.

  • LMS 4.2.4 Baseline template deploy fails for 2960X

    Hello,
    we have Cisco Prime LMS 4.2.4 and I added a new switch type C2960X-24TS-L with IOS Version 15.0.2-EX1.
    I'd like to deploy a baseline template, but it fails:
    Protocol ==> Unknown / Not Applicable
    Selected Protocols with order ==> SSH,Telnet,TFTP
    Execution Result:
    CM0150 Deploy Baseline template to PRIMARY config on device failed Cause: Operation not supported for generic support devices
    CM0056 Config fetch failed for xxxxx Cause:
    PRIMARY-RUNNING config Fetch Operation failed for TFTP.
    SSH: Failed to establish SSH connection to 10.xxx.xxx.xxx - Cause: Authentication failed on device 3 times.
    Action: Check if protocol is supported by device and required device package is installed.
    The device is reachable via telnet.
    I think that I installed the latest device packages for LMS 4.2.4.
    What could be the problem here?
    Thanks,
    Kerstin

    Hi Afroz,
    when I checked the ssh-credentials, I got a failure on ssh enable.
    The failure message on ACS is "missing user password".
    I reentered the credentials, but the error persists.
    I tried to login with the credentials manually, and it works. So the credentials are correct.
    Last I deleted and re-added the device, but nothing has changed.
    Other devices (not 2960X) working correct.
    So I think maybe I haven't the latest device packages for 2960X-Switches. But here is the next problem, I can't check for latest packages:
    [ Tue Apr 07 12:19:10 CEST 2015 ] INFO   [DownloadManager : queryAllPkgs]  : Going to collect download packages...
    [ Tue Apr 07 12:19:12 CEST 2015 ] ERROR  [RemoteRepSync : downloadPsuHeadersAsXml]  : VDSException thrown com.cisco.nm.xms.vds.VDSException: CcoDownloadAdapter::getXmlFileList():IOException:tools.cisco.com
    Regards,
    Kerstin

  • Gmail, Mail.app and Archive Failing

    One of my parents' macs fails to properly archive email messages.  Gmail is acting as the backend, and I used the recommended imap settings from Google to set up the account.  The error message is this:
    "The IMAP command “UID COPY” (to Archive) failed for the mailbox"
    Any ideas?

    Take a look here: http://www.imore.com/how-to-gmail-2-step-verification-mail--iphone--ipad-mac

Maybe you are looking for