Partially Collected Config Archive

Hello,
For 3 switches config archive is partially collected,After searching from enough threads i have done the below but still no sucess
i have given enough rights to tftpboot dir for caususer
created a vlan.dat in tftpboot folder
manually copied vlan.dat from switch to the file in vlan.dat
start a job of syn but no sucess.
Any hints experts.
Thanks

Dear's
Waiting for ur replies??
Thanks.

Similar Messages

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

  • Ciscoworks unable to collect config in RME due to firewall?

    My CW is unable to collect the config in RME
    I'm using CDP, OSPF, and BGP for discovery..
    I udnerstand that CW use snmp read community string to discover network devices. I can see CW pick up the devices in the device management list, but when I do a ssh credential check, the devices behind the firewall fails. The snmp R & W credentials are correct I can logon to the network device using the primary account without an problem. What could be the problem? What do I need check/perform in order to collect the aconfig for archive. Do I need to open a port on the firewall for CDP traffic? Other devices (not behind the firewall) works fine.
    Your input is greatly appreciated.

    Im running RME 4.3.1
    Attached is the screenshot [2] of unsuccessful configs archive and inventory collection failures.
    Here are e error messages:
    SH: Failed to establish SSH connection to 10.x.x.x - Cause: Read timed out. TELNET: Failed to establish TELNET connection to 10.x.x.x - Cause: connect timed out.
    Could not detect SSH protocols running on the device TELNET: Failed to establish TELNET connection to 10.x.x.x - Cause: connect timed out.
    Could not detect SSH protocols running on the device TELNET: Failed to establish TELNET connection to 10.x.x.x - Cause: connect timed out. Failed to fetch config using TFTP Failed to fetch config using RCP.Verify RCP is enabled or not. Failed to fetch config using SCP.Socket closed Verify SCP is enabled or not.
    I can logon (using putty) without a problem using the same account.

  • Prime Infrastructure 2.0: Inventory Collection - Partial Collection Failure on 2 of 4 VSS WS-C6509-E

    Hello,
    I've got a strange behaviour regarding the inventory collection for 2 of 4 virtual switching systems.
    That means the inventory collection for two VSS is succesfull (inventory collections status = Completed) for the other two systems it is not, see attachments.
    The device credentials like SNMP-RW, SSH acces are OK. I've already tried to increase SNMP timout and retries as well as telnet/ssh timout without success
    All 4 systems are identical regarding hardware model and software vesion.
    HW: WS-C6509-E
    SW: 12.2(33)SXJ3
    Any ideas or suggestions?
    Best regards,
    Bastian

    TAC and I found a bug, CSCum05301.
    May be that is also helpfull for others.
    https://tools.cisco.com/bugsearch/bug/CSCum05301/
    Symptom:
    Inventory collection will fail if following keywords are used as part on description command on the interface config level of IOS device: 1Gbps, 10Mbps etc.
    Following error message is visible on the DWC:
    Inventory Collection Status: Partial Collection Failure
    Collection Status     Failed feature(s)
    Unable to configure DSL, Serial, POS, Ethernet, Loopback, Virtual-Interface, Tunnel, Vlan, Switchport and Service Module interfaces on ISR, ASR and Switches.
    Conditions:
    Speed keywords like 1Gbps, 10Mbps etc. available as part of descrption command in IOS interface level.
    For example:
    interface FastEthernet0/3
    description 10Mbps
    Workaround:
    Use a space character between number and unit keyword, like 1 Gbps.

  • Prime Infrastructure 2.1 ASA5580- Security Context Partial Collection Failure

    I am attempting to add my ASAs into prime but get stuck almost instantly after adding the new device. Prime is able to get the device name and Device type (Cisco ASA-5580 Adaptive Security Appliance Security Context) Admin status shows up as Managed but Inventory Collection Status shows up as "Partial Collection Failure" For more detail it says "feature_image_firewall Unexpected error. See the log file inventory.log for details."
    The only failure in inventory.log I could find was
    [2014-09-26 12:40:01,868] [ICE Service[ 1]Thread: 20] [inventory] [ERROR] - 192.168.0.19 For device id: 2848866 Feature = feature_image_firewall and Procedure = ImageFireWal failed in time 45 with the following error and continuing with other features: com.cisco.nm.expression.function.FunctionException: <palError><deviceId>2848866</deviceId><code>HANDLER_ERROR</code><message>Error while trying to run handler. Action : imageFireWall, Handler : com.cisco.nm.pal.customhandler.RPLHandler. Error : Exception thrown : Constraint violation. See log for details.</message><handlerCode>ERROR_HANDLER_ERROR</handlerCode></palError>
    [2014-09-26 12:40:01,868] [ICE Service[ 1]Thread: 20] [ice] [ERROR] - com.cisco.nm.expression.function.FunctionException: <palError><deviceId>2848866</deviceId><code>HANDLER_ERROR</code><message>Error while trying to run handler. Action : imageFireWall, Handler : com.cisco.nm.pal.customhandler.RPLHandler. Error : Exception thrown : Constraint violation. See log for details.</message><handlerCode>ERROR_HANDLER_ERROR</handlerCode></palError>
    com.cisco.nm.expression.function.FunctionException: <palError><deviceId>2848866</deviceId><code>HANDLER_ERROR</code><message>Error while trying to run handler. Action : imageFireWall, Handler : com.cisco.nm.pal.customhandler.RPLHandler. Error : Exception thrown : Constraint violation. See log for details.</message><handlerCode>ERROR_HANDLER_ERROR</handlerCode></palError>
    As far as the ASA config goes:
    snmp-server enable
    snmp-server host management 192.168.10.27 community c!$c0PR!me version 2c
    logging enable
    logging history 7
    snmp-server enable traps
    The above config works on our ASA5520s except I still haven't set up the traps right because there isn't any useful information on those devices so I am not sure what I need to change?

    My ASA is using DH 1.
    For 9.2(1) I read this in the release notes.
    Note The ASA 5510, ASA 5520, ASA 5540, ASA 5550, and ASA 5580 are not supported in this release or later. ASA Version 9.1 was the final release for these models.

  • 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

  • Partial collection Failure for nexus 5548UP in PI 2.1

    Hi there,
    I get "Partial Collection Failure" in the inventory collection status in Prime Infrastructure for all my Nexus 5548UP (8 devices).
    i have seen in the PI 2.1 release notes that a bug CSCum16230  which look like my problem has been resolved in PI 2.1 but i continue getting the "partail collection failure"
    Would like to know if the bug is still exist or get any other help to solve this problem.
    Regards,
    Alon.

    hello
    I have this problem as well...
    we've got four N5K-C5548UP. Two with a layer 3 daughter card and two without.
    interestingly we see the issue just on those boxes with the l3 daughter cards N55-D160L3-V2 installed...
    Any help or ideas are highly appreciated
    regards
    roman
    Sh inventory:
    OK:
    device-a# sh module
    Mod Ports Module-Type Model Status
    1 32 O2 32X10GE/Modular Universal Pla N5K-C5548UP-SUP active *
    3 0 O2 Non L3 Daughter Card N55-DL2 ok
    Mod Sw Hw World-Wide-Name(s) (WWN)
    1 5.1(3)N2(1c) 1.0 --
    3 5.1(3)N2(1c) 1.0 --
    NOT OK:
    device-b# sh modu
    Mod Ports Module-Type Model Status
    1 32 O2 32X10GE/Modular Universal Pla N5K-C5548UP-SUP active *
    3 0 O2 Daughter Card with L3 ASIC N55-D160L3-V2 ok
    Mod Sw Hw World-Wide-Name(s) (WWN)
    1 5.1(3)N2(1c) 1.0 --
    3 5.1(3)N2(1c) 1.0 --

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

  • Cisco Prime 2.1- Partial collection failure

    Dear Experts,
    We are seeing many devices (around 1000+ devices) showing as "partial collection failure". We found this coz of not updated Telnet/SSH Cli username and password. So instead of editing each and every device, is there any way to select all devices and update cli credentials in one shot..?
    If someone helps me this option, it will be so helpful.

    Hi ,
    Other way is to export all the devices , Edit it and then Import it.
    Operate >device workcenter >   EXPORT device \ BULK IMPORT
    Thanks-
    Afroz
    ****Ratings Encourages Contributors ****

  • Prime Infrastructure 2.1 - Config Archive

    In PI2.1, is it possible to send the config archive of my devices to a network drive?  TIA

    PI will always save the configurations into its database. That database is always on the PI server itself.
    You can export the configurations from the database via a manual process - you could probably script it and kick it off via cron if you are handy with that sort of thing.
    The export process is explained in a post by Vinod Arya in the Prime Infrastructure Ask the Expert thread.
    (Edit - corrected link)

  • 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

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

  • RME config archive collection status failed

    I can use the logon account to telnet/ssh to the device, but why does the log says it could not detect telnet/ssh?
    Cat1-6509   VLAN    RUNNING   Dec 29 2009 19:54:04    Could not detect SSH protocols running on the device TELNET: Failed to establish TELNET connection to 10.172.x.x - Cause: Authentication failed on device 3 times.
    Cat2-6509  PRIMARY  RUNNING  Dec 29 2009 19:53:45  Could not detect SSH protocols running on the device TELNET: Failed to establish TELNET connection to 10.172.x.x - Cause: Authentication failed on device 3 times.
    Any assistance would be greatly appreciated

    RME cannot connect to the device using the credentials in DCR.  Export the credentials from Common Services > Device and Credentials > Device Management, and verify you can connect to the device and become enabled using those credentials.  If you can, then start a sniffer trace filtering on all telnet traffic to the device in question, and run a new sync archive job.  When it fails, post the capture file.

Maybe you are looking for