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

Similar Messages

  • 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.

  • 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

  • Cisco Prime 2.2 Config Archive get Partial-Success

    Good morning everyone!
    I have a question regarding Cisco Prime Infrastructure 2.2 and Config Archive. Im trying to backup a configuration for an old WS-CBS3020-HPQ blade with IOS version 12.2(58)SE1 and im getting an error under "Fetch vlan" that says :
    Couldn't able to collect VLAN on the device. TFTP server not accessible from device.
    Im not sure what this means? It gets partial-success, but the error message worries me. Im not able to find anything in the logs or by searching for the error code. Anyone have any idea where to look? The credential is correct, i tripple checked :)

    I tried using the "tftp-server flash:" command, but didnt help. Im also seeing this problem with a couple of Cisco 3750x switches.

  • 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.

  • 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

  • RME config archive problem - lms 3.2

    just wondering if anyone else has seen this.
    about a month or so ago, I grabbed about 6 or 7 patches for our ciscoworks machine, across cm, rme, and cs. (yeah, we were a little behind)
    after applying these patches, it seems, all of the 2960s and 4948s are failing the config archive with the following:
    cm00139: could not archive config:cause: action: verify that device is managed and credentials are correct. Increase timeout
    value if required.
    so I've triple checked the credential set applied to these devices, adjusted timeout and retry values, and have gotten nowhere.
    Deleting these devices doesn't seem to help, they are rediscovered just fine, but the config archive continues to fail.
    Other than maybe trying to reinstall the rme patches (or uninstall) that were recently applied, I'm out of ideas. This is LMS 3.2.1 with
    cm 5.2.2
    cs 3.3.1
    rme 4.3.2
    running on windows server 08.
    So if anyone may have seen this and/or has any advice, I'd appreciate it. Thanks - chris

    ok, so it's been a year and a half since last post. So in addition to the above mentioned archive failures with the 4948s, the 4948s were also showing up in config out of sync summary. The only difference that were showing between running and startup was the ntp clock period.
    I did see that the clock period statement was in the exclude list for routers and a bunch of other things, but not for the 4948s. I added this as an exclusion yesterday. Today when I checked, all 4948s are archiving now, and are off the out of sync report. Never would have crossed my mind to check there, but that exclusion seems to have done the trick. Maybe someone else can use this if they're seeing the same thing. - chris

  • VLAN RUNNING Config fetch Failed

    Hi;
    I have running Ciscowork LSM 3.2 with RME Ver 4.3 and Running SNMP V3 on all device. Out of 134 device 12-13 shows me Vlan running Config fetch failed. Please also find the dcmaservice.log in attachment.
    I already verify the Crediential number or times, I can access the devices from SSH and Telnet, on Cisco works RME shows Running and Startup Config success while VLAN Running Config fetch failed. and on some device it show following
    Protocol and Platforms passed = TELNET , RMEIOS
    trying for Telnet
    Failed to get CmdSvc from DeviceContext....
    Thanks,
    Best regards;
    Shoaib Ahmed

    HI Shoaib,
    Try  ssh\telnet into the device manually and issue the command copy flash:vlan.dat tftp: and
    enter the IP address of the LMS server? Does it work? If that works fine, try to increase
    the tftp timeout.
    This can be done under RME> Admin> System Preferences> RME Device Attributes.
    if it failed with an Error as below :
    %Error opening tftp: ............
    Then check if there any firewall in between these device and LMS blocking TFTP as TFTP is the only protocal
    that fetch the vlan.dat from the device.
    Thanks--
    Afroj

  • Utils import config command failed on CUCM8.6.1

    I've created cucm861sub.flp file and uploaded it to the datastore on ESXi 4.1, then mapped to the floppy, i.e. I followed procedure on cisco wiki to the last letter. Still, after applying command I'm receiving following error: "Cannot locate configuration file"
    I've used Winimage to crate 1.44MB floppy that contains only one file, called platformConfig.xml (file was downloaded directly from CCO).
    Was anybody able to apply successfully new identity feature?

    I opened a TAC case and found this is a bug.  CSCtx55507 :utils import config" is failing.
    these are the call manager versions that has the fix for this issue:  8.6(2.10000.30), 8.6(1.98000.87), 8.6(1.98000.39) or any later  version.

  • Cisco lms - config collection

    Hi, i'm looking for a way to collect config's from specific devices periodically, is this possible?
    for example, collect configs from firewalls everyday at midnight , and collect routers config once a week.
    firewalls: (about 3 devices, config changes every day)
    routers: (about 800 devices, rarely change the config)
    the only config collection schedule i have found so far is too simple:
    admin > collection settings > config > config collecion settings > periodic collection
    second question, is it possible for cisco lms to send via e-mail the diff of the config pulled from devices? i mean the specific commands that have appeared in the new configuration file.
    regards, ignacio

    Unfortunately, LMS syslog mechanism is very minimalistic and doesn't have a lot of options to it.
    However, the feature you're requesting is not very much LMS dependent. As, Ciscoworks depends on the kind of syslog message it receives from device, based on it, it captures some characters to send a notification as automated actions.
    So usually it is the device which won't send a lot of information on what changes was done by which user in normal IOS syslog messages.
    But, to certain extent, you can try to configure you device for Configuration-Change logger to receive details on what changes were made by users and check it on the syslog report, or configure AA on it for all or important devices.
    You can enable a configuration logger to keep track of configuration changes made with the command-line interface (CLI). When you enter the logging enable configuration-change logger configuration command, the log records the session, the user, and the command that was entered to change the configuration. You can configure the size of the configuration log from 1 to 1000 entries (the default is 100). You can clear the log at any time by entering the no logging enable command followed by the logging enable command to disable and reenable logging.
    Use the:
    show archive log config {all | number [end-number] | user username [session number] number [end-number] | statistics} [provisioning] privileged EXEC command to display the complete configuration log or the log for specified parameters.
    This example shows how to enable the configuration-change logger and to set the number of entries in the log to 500:
     Switch(config)# archive 
     Switch(config-archive)# log config
     Switch(config-archive-log-cfg)# logging enable
     Switch(config-archive-log-cfg)# logging size 500
     Switch(config-archive-log-cfg)# end
    So, in all, it depends on the device and the kind of syslogs it send for LMS to react on it.
    -Thanks
    Vinod
    **Encourage Contributors. RATE Them.**

  • Cisco Prime Configuration Archive on Interface Flap

    Hey All,
    We've been using Cisco Prime 2.1 for a bit now and I have a question about the configuration archive based on change events.  Will Cisco Prime go and attempt to perform a config backup based on an interface flap?  Looking at the audit logs it appears that it does that (see attachment).  Is this a default behavior and does anyone see any benefit to this?  It seems like if an interface is flapping it will continuously log into the device to see if the configuration has changed.
    Brian

    Hi Brian,
    I don't think configuration achieve can be triggered due to interface flap ,however if there is any change in the configuration yes PI can do the config Archive
    Go to Administration > System Settings > Configuration Archive
    Archive Configuration on receiving configuration change events?    Check box this option
    Thanks-
    Afroz
    ***Ratings Encourages Contributors *****

  • 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,

  • Login to cisco CME as Administrator failed check your call manager express

    Hi Experts
    CME and CUE in one router. when i access the CUE from the IE , i put the CUE username and password and i get in. After that it asks me to enter CME username and password to run the wizard. whenever i put the password i get this crappy message "Login to cisco CME as Administrator failed. check your call manager express config" i have cheked my config many times. Please let me know if someone has faced this problem or any suggestion on this. today is the 2nd time i have faced this problem , last time I cud not solve it and end up wasting 6 hours...
    please help

    Hi friend,
    Here is the Prerequisites for Installing Cisco Unity Express Software. As David describes, may be the CME admin account is missing:
    http://www.cisco.com/en/US/docs/voice_ip_comm/unity_exp/rel3_1/installation/guide/prereq31.html#wpmkr1112912
    Try this, and let us know.
    Best regards,
    - Adrián.

  • Config Archive for Call Manager

    Hello,
    It give me the attahced error fo r config archive for call manager.

    The supported devices page shows each supported device, and what features are supported:
    http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/3.2/device_support/table/lms32sdt.html

Maybe you are looking for

  • CLEAN_REQREQ_UP dumps with "LOG_NOT_FOUND" exception

    Hi all, When I run the CLEAN_REQREQ_UP program, I get a dump with exception "LOG_NOT_FOUND" from the function module BBP_PD_LOG_DELETE. I saw a OSS note 1121892 but the symptom says "You deleted some Logs with the Transaction SLG2. Afterwards you run

  • No remote connection

    Hi,  I've done a number of SQL 2008R2 installs before and have never had a problem, however today I have had to install on Windows server 2012 (argh!!!) and can't seem to get connections from my local SSMS.   I have enabled connections, checked the p

  • Combobox in FlashLite 2.1

    Is it possible to use a combobox inFlash Lite 2.1? It's only working when I use a Flash 6 File on the PDA but not a FL2.1 file? thx KH

  • Huge number of V2 updates // report RSM13005

    Hi, There's around 3000++ V2 update records found in one of the production system. Is this normal?? What triggers such an alarming no of V2 update records? Any way to check this? Also could it be related to the report RSM13005  which is not scheduled

  • FRM-18108 Failed to load the  objects

    I have upgraded the forms from 4.5 to 6i and when I tried to open the form PCOECU20 it gives me error FRM-18108 Failed to load the following objects: Source Module: PCOEar10 Source Object: STRUCTURE_NAME_QF_LOV Source Object: pc_object_Group1 ... and