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.

Similar Messages

Cisco Prime Infrastructure Scheduled Configuration Archive not executing

We have a deployment of Cisco Prime Infrastrcuture 1.3 (1.3.0.20).
Configuration Archive is a feature that collects and archives the device configurations i.e. cisco switches.
You have an option to schedule this to run, say daily, weekly etc. Once scheduled you can see it in the "Jobs Dashboard" and with the "next start time" of what you configured. I have a situation whereby the time it is suppose to start - it doesnt - howevere flags the job as a "success". Not newe device configurations are archived and the "next start time" remain the same. Its almost like it is failing to execute, but some other process under the hood thinks that it was been executed correctly?
Any ideas or experience that could help here would be appreciated!

Some extra info that has just come to my attention. At one point we were running (we're actually still running) CiscoWorks with LMS3.2 and Cisco NCS 1.x. I merged these two things together into Cisco Prime Infrastructure (upgraded the licensing to get 450 lifecycle licenses to cover the APs + all of the devices coming from LMS3.2). I followed all of the documented procedures to upgrade the NCS appliance to Prime Infrastructure. But when I type "show application" from the CLI of the NCS appliance (now the Prime Infrastructure appliance) I see this:
HQ-NCS1/admin# show application
NCS Cisco Prime Network Control System
Is that normal? Maybe this is my problem. Should this output list "Cisco Prime Infrastructure" instead of (or in addtion to) Cisco Prime Network Control System? When I login to the GUI it shows "Cisco Prime Infrastructure" and the GUI has changed considerably (menus are different) so I'm assuming that the application upgrades I launched from the CLI to go to Prime Infrastructure worked fine.

CiscoWorks: Why all devices Sync archive only partially successful.

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

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

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.

Cisco Prime 2.1 CLI-Template for Switch configuration Backup

Hello everybody,
I am trying to write a CLI Template in cisco Prime to save the running-configuration of our core switch to the FTP server,
I have already configured the FTP username and Password in the core Switch
ip ftp username cisco
ip ftp password cisco123
in Cisco Prime I have created a template as follow:
copy running-config ftp:
$FTP_IP_addrress >> the FTP Server
$name >> the name of file and the date
After deploying this template on the core switch,
I received Error Msg in Prime as follow:
Error : Command returned an error : copy running-config ftp: 172.16.30.30 Run_Config_Core_19_2_2015 ^ % Invalid input detected at '^' marker. QAF-DC-4507-CORE(config)#
I know that the backup files can be fetched directly from Cisco Prime in the Configuration Archives, But also I need to test if we can take a backup directly to the FTP server using Prime.
Thanks in advance.

Thank you Bkennedy for replying,
I changed my template to be as follow:
#MODE_ENABLE
copy running-config ftp:
$Mgmt_IP_addrress
$name
#MODE_END_ENABLE
but still I am receiving Error like :
Error : Exception while sending interactive commands to device, Expect timeout: Failed to match expected device output due to Expect timeout current timeout 60000. Current output : Address or name of remote host []? Current expects : (DC-450.{0,30}|DC-4507-AGG)$[^$]+\)#\s*\z DC-4507-AGG#
I believe that we have to tell the Prime how to send the variables to Switch, because the switch is waiting for the remote host IP address and the destination file name???
DC-4507-AGG#copy running-config ftp:
Address or name of remote host []? X.Y.Z.W
Destination filename [dc-4507-agg-confg]?
% VRF table-id 0 not active
% VRF table-id 0 not active
Writing dc-4507-agg-confg !
24425 bytes copied in 1.500 secs (16283 bytes/sec)
DC-4507-AGG#

Cisco Prime Infrastructure 1.2 Error

Hi,
I don't have any experience with Cisco Prime infrastructure. I am getting the below error
Unable to start secondary NCS server PRLPrimeNCS02 [10.140.xx.xx]
Reason: IO Error: could not resolve the connect identifier "wcss1"
Not sure exactly what the error means. Any help much appreciated.
Thanks
Nachi

Hi Scott,
Thank you for your email.
The HA is runing on the Cisco Prime. Runing Cisco Prime on a Virtual machine in VM.
The issue we are experiencing is that the system failed over to the secondary (HA) for unknown reasons. When we failed it back it didn’t fail back properly. Configured Manual failover. Managed to failback to primary but it complained HA was no longer configured.
Tried to remove HA and reconfigure it. The primary removed the HA configuration, but the secondary kept it. Here is some info on the secondary
PRLPrimeNCS02/admin# ncs ha status
[Server] prlprimencs01(10.xx.xx.xxx) [State] Secondary Lost Primary [Failover Type] manual
PRLPrimeNCS02/admin# ncs ha remove
High availability configuration will be removed
Do you wish to continue? (y/N) y
Removing secondary configuration will remove all database information
Do you wish to remove high availability configuration from primary? (y/N) y
Secondary is attempting to remove high availability configuration from both primary and secondary
Requesting primary to remove high availability configuration from both primary and secondary
Successfully removed high availability configuration
PRLPrimeNCS02/admin#
PRLPrimeNCS02/admin#
PRLPrimeNCS02/admin# ncs ha status
[Server] prlprimencs01(10.xx.xx.xxx) [State] Secondary Lost Primary [Failover Type] manual
PRLPrimeNCS02/admin#
And the primary
prlprimencs01/admin# ncs ha status
[State] Stand Alone
prlprimencs01/admin#
Below is the log
Starting Health Monitor as a secondary
Checking for Port 8082 availability... OK
truststore used is /opt/CSCOlumos/conf/truststore
truststore used is /opt/CSCOlumos/conf/truststore
Starting Health Montior Web Server...
Health Monitor Web Server Started.
Starting Health Monitor Server...
Health Monitor Server Started.
java.lang.OutOfMemoryError: Java heap space
Dumping heap to logs/java_pid6044.hprof ...
Heap dump file created [249907589 bytes in 6.857 secs]
Thanks
Nachi

FIne Tuning the Cisco Prime Alarms

HI Expert,
One of our client having Cisco Wireless LAN infrastructure with Cisco Prime. Currently they are getting more alarms (minor) on their environment.
They would like to modify the Alarm pattern / threshold to minimise the Alarms pop-up in prime. Could you please advise me how we can modify this ?
Also do Cisco having any documents for how to fine tune ?
Thank you.
-Ananthan

Hi
Here's the document for the customization of alarms.
Configuring Alarm Severity Levels
A newly generated alarm has a default severity level that you might want to change.
To configure an alarm’s severity level, follow these steps:
Step 1 Choose Administration > System Settings.
Step 2 From the left sidebar menu, choose Severity Configuration.
Step 3 Select the check box of the alarm condition whose severity level that you want to change.
Step 4 From the Configure Security Level drop-down list, choose a severity level, then click Go.
Step 5 Click OK to confirm the changes.
Configuring Alarm Severity Levels
http://www.cisco.com/c/en/us/td/docs/net_mgmt/prime/infrastructure/2-2/user/guide/pi_ug/alarms.html#pgfId-1054721
- Ashok
Please rate the useful post or mark as correct answer as it will help others looking for similar information

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 *****

Cisco Prime 2.1 Archive Search

in past versions of CiscoWorks I was able to search configuration archives.
Config MgmtArchive MgmtSearch Archive
Can I do that with Cisco Prime 2.1???

You can thin provision. Trying to change the overall profile though will most likely result in issues sooner or later. When you run out of disk space it will fail in ungraceful ways.

Cisco Prime 2.1.2 auto sync config for switches and Routers

hello Support,
how to configure auto sync config in CPI? when the customer make a changes in the switches and Routers, the customer expect a new version of the configuration in CPI immediately. but we are getting the new version after 10 minutes. if we not configure in the switches and Routers to send syslog we are not getting anything.
where we have to configure in CPI to get the new versions immediately?
thanks!

Make sure you have completed the recommended preparation steps given in Before You Begin Installing the Patch.
If you are not using the Prime Infrastructure High Availability (HA) feature, follow the steps in Installing the Patch instead of the steps below.
If your current Prime Infrastructure implementation has High Availability enabled, follow the steps below to install the patch. You must start the patch installation with the primary server in “Primary Active” state and the secondary server in “Secondary Syncing” state.
Patching of the primary and secondary servers takes approximately one hour. During that period, both servers will be down. If you have trouble at any point, see Troubleshooting Patch Installs in HA Implementations.
Step 1 Ensure that your HA implementation is enabled and ready for update:
a. Log in to the primary server using an ID with Administrator privileges.
b. Select Administration > System Settings > High Availability , The primary server state displayed on the HA Status page should be “Primary Active”.
c. Select HA Configuration . The current Configuration Mode should show “HA Enabled”.
d. The Failover Type must be set to “Manual” throughout the patch installation. If Failover Type is currently set to “Automatic”, select “Manual” and then click Save .
e. Access the secondary server’s Health Monitor (HM) web page by pointing your browser to the following URL:
https:// <ServerIP> :8082
where ServerIP is the IP address or host name of the secondary server.
f. You will be prompted for the authentication key entered when HA was enabled. Enter it and click Login .
g. Verify that the secondary server state displayed on the HM web page is “Secondary Syncing”.
Step 2 Download the patch:
a. Point your browser to the software patches listing for Cisco Prime Infrastructure 2.1.
b. Click the Download button for the Release 2.1.2 patch file (pi212_20141118_01.ubf), and save the file locally.
Step 3 Install the patch on the secondary server:
a. Access the secondary server’s HM web page by pointing your browser to the following URL:
https:// <ServerIP> :8082
where ServerIP is the IP address or host name of the secondary server.
b. You will be prompted for the authentication key entered when HA was enabled. Enter it and click Login .
c. Choose the HM web page’s Software Update link. You will be prompted for the authentication key a second time. Enter it and click Login again.
d. Click Upload Update File and browse to the location where you saved the patch file.
e. Click OK to upload the patch file.
f. When the upload is complete: On the Software Upload page, verify that the Name, Published Date and Description of the patch file are correct.
g. Select the patch file and click Install . When the installation is complete, you will see a popup message confirming this.
h. After the installation is complete on the secondary server, verify that the Software Updates page shows:
– In the “Installed” column: A “Yes” opposite the listing for this patch.
– In the “Pending Restart” column: A “Yes” for the secondary server. Do not restart the secondary server at this point.
Step 4 Install the patch on the primary server:
a. Log in to the primary server using an ID with administrator privileges and choose Administration > Software Update .
b. Click Upload Update File and browse to the location where you saved the patch file.
c. Click OK to upload the patch file.
d. When the upload is complete: On the Software Upload page, verify that the Name, Published Date and Description of the patch file are correct.
e. Select the patch file and click Install . When the installation is complete, you will see a popup message confirming this.
f. After the installation is complete on the primary server, verify that the Software Update page shows:
– In the “Installed” column: A “Yes” opposite the listing for this patch.
– In the “Pending Restart” column: A “Yes” for the primary server. Do not restart the primary server at this point.
Step 5 Stop the servers in the following sequence, using the commands explained in Running Commands:
a. On the secondary server, run the ncs stop command.
b. On the primary server, run the ncs stop command.
Step 6 Re-start and monitor the servers in the following sequence, using the commands explained in Running Commands:
a. On the secondary server, run:
– The ncs start command to restart the secondary server. Wait for the processes on the secondary to restart.
– The ncs status command to verify that the processes on the secondary have re-started.
– The ncs ha status command to verify that the secondary state is “Secondary Lost Primary”.
b. Once the secondary server is in “Secondary Lost Primary” state: On the primary server, run:
– The ncs start command to restart the primary server. Wait for the processes on the primary to restart.
– The ncs status command to verify that the primary’s Health Monitor and other processes have re-started.
Once all the processes on the primary are up and running, automatic HA registration will be triggered. This normally completes after a few minutes.
Step 7 Once registration completes, verify the patch installation as follows:
a. Run the ncs ha status command on both the primary and secondary servers. You should see the primary server state change from “HA Initializing” to “Primary Active”. You should see the secondary server state change from “Secondary Lost Primary” to “Secondary Syncing”.
b. Log in to the primary server and access its Software Update page as you did earlier. The “Installed” column should show “Yes” and the “Pending Restart” column should show “No” for the installed patch.
c. Access the secondary server’s Health Monitor page as you did earlier. The “Installed” column should show “Yes” and the “Pending Restart” column should show “No” for the installed patch.

How can I get CDP neighbor information from access point reports in Cisco Prime 2.0

How can I get CDP neighbor information from access point reports in Cisco Prime 2.0? I have looked through all the reports and I cannot find a report that gives me the CDP neighbor information of an access point. I thought that information was in there, however I cannot seem to find it.
Thanks in advance!

Hi
You can get this from an inventory report in PI (Select Report Type AP). Here is an example of PI 2.1 works for me. Once you export this into excel you can sort based on controllers & filter the single controller connected AP you want.
Regards
Rasika
**** Pls rate all useful responses ****

Cisco Prime Infrastructure 1.3 - SNMPv3 can´t get CPU, memory info.

Hi,
I have a Cisco Prime Infrastructure 1.3 deployment with Catalyst 2960S switches. Switches are running IOS 15.0(2) SE2. All switches have SNMPv2 configured, and all appears to be fine. I'm migrating one switch to SNMPv3, and PI have reachability to the switch, but PI doesn´t receive traps from the switch, and neither poll CPU and memory information (all displays 0.00%).
Somebody have a sample configuration of SNMPv3 with Cisco Prime (Infrastructure or LMS)? I cannot find a Cisco official (or unofficial) document related to this version, usually all mention SNMPv2.
Thank you.
Eduardo

Hi Eduardo:
SNMPv3 is indeed supported for general administration. There's a bug with SWIM using SNMPv3 (CSCud92758), but you should be fine for just monitoring. Have you deleted the switch, waited until Prime Infrastructure told you it was gone, then readded it as SNMPv3 natively? Bug CSCug78869 keeps things from working well when changing SNMP versions.
If you don't have the new Update-1 patch for Prime Infrastructure 1.3.0.20 installed (filename PI_1.3.0.20_Update_1-12.tar.gz) installed, I'd suggest you get it. While it's not going to specifically address this issue, there are a lot of really good fixes in it.
Release Notes for Update 1 for Cisco Prime Infrastructure 1.3.0.20

Getting past "Fetch VLAN configuration - Command failed" errors in Cisco Prime Infrastructure 2.0 - How?

I've got a handful of devices in Cisco Prime Infrastructure 2.0 which show up in the "Archive Failed Devices" view. The "Failure Reason" is some variation of "Fetch VLAN configuration - Command failed" sometimes including "TELNET: Failed to establish TELNET connection to x.x.x.x". What does this mean? How do I overcome this? In all cases, the device is configured to use SSH and has valid SSH credentials. In all cases, I can SSH from the command line of the NCS appliance to the devices listed in the "Archive Failed Devices" view.

Hi
I was able to fix the "Fetch VLAN configuration - Command failed" by allowing tftp from the device to PI server in firewall. See if this can help.

Cisco Prime Infrastructure release 2.1 configuration archiving on CISCO WiSM2

Hi all,
Just wondering Cisco Prime Infrastructure release 2-1 support configuration archiving on CISCO WiSM2?
CISCO release 2.0 mentioned that it doesn't support configuration archiving for WiSM2 but release 2.1 doesn't mention anything on it.
Please assist.

No, it is not supported even for PI 2.1

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)

Cisco Prime 2.2 Config Archive get Partial-Success

Similar Messages

Maybe you are looking for