LMS 3.2 in solaris

Hi,
We are using LMS 3.2 in Sun platform.In which directory LMS archiving the configuration files of all the routers,under shadow directory i am able to find few routers configuration and also i need to have date wise configuration.Through GUI in version tree am able to find the configuration.
I enabled data collection one day once.
Please guide me for this
Regards,Bala

Hi Bala,
Yes you are right the Location of the backup configuration files on solaris is:
On Solaris, /var/adm/CSCOpx/files/rme/dcma/shadow
In this location as soon as cisco works found a change in your device configuration it will backup the configuration file in this location itself.
Configuration backup is not a part of DataCollection.
You need to configure the SYNC-ARCHIVE job (RME > config mgmt ) for archive collection \ configuration backup.
I hope this will help..
Thanks
Afroj

Similar Messages

LMS 3.1 on Solaris 10 - Reset all databases to initial state

Hi,
Is there a script that would clear all databases for LMS 3.1 on Solaris 10?
I imported do CS some devices from a CSV file I exported from an old LMS 2.5 server we had. I get some very strange results when I ask to sync archive for instance. The devices I manually added work fine, but the ones I imported get stuck and the job takes forever to finish (10 hours in some instances, for 230 devices).
I'd like to re-start from scratch without having to uninstall and reinstall LMS.
Thanks,
Jose Ribeiro
MGS

See this DOC for the commands to reinitialize all databases.

Backup problem with LMS 3.0 on Solaris

Hi All,
I'm encountering problems with LMS 3.0 when I try to do a backup. After you hit OK on the window that says "Do you want to backup now?", an error would pop up saying: "Enter a new directory name or ask the system administrator of the Ciscoworks Common Services server to make the directory accessible to user casuser", thus I cannot proceed with the backup process. When I do backup, my login privilege is admin. Even tried to do backup on the same partition as my CSCOpx directory but to no avail.
Appreciate your help on this guys. Our LMS 3.0 runs on Solaris platform. Thanks in advance.

Hi Joe,
Thanks for your prompt response. By the way, what is a casuser? Is he also one of the user that can be found on the Local User Setup on Common Services? The scenario here is that, I am not the one who installed the Ciscoworks LMS 3.0 on the client side, so I am not aware on how they did the installation procedure for the application. I remember assigning casuser password during installation on our other clients that has LMS 3.0.
Will the write access on the backup directory for the casuser be done by the Solaris root administrator?
Thanks for your help.

CISCO LMS 4.0 on solaris 10

Hello everyone my name is Eric and I have some issues with our LMS 4.0.
We have installed it on a Solaris 10 non global zone on a Solaris 11.1 server.
It runs and the webgui is accessible.
I did an export of the data from the old server and a bulk import to the new one. It ran and added the data but you don't see it in inventory, when you try to run a credential validation on any device it tells you theres nothing in the DCR. I manually added the seeds but still no joy.
I attempted to make it a slave of our old LMS 4.0 virtual installation but it didn't replicate any data.
I then attempted to restore/migrate the data from the old serve to the new one but when running the /op/CSCOpx/bin/perl /opt/CSCOpx/bin/perl/restorebackup.pl -d "backup_directory" script I recieved the:
ERROR MAXENV value reached, fix this perl wrapper!
I found nothing on a google search related to this issue with perl.
I have attempted to manually load the DCR and run discovery but when I do it only finds 6 devices 5 of which are unreachable.
I think I have exhausted all the avenues I have to get this thing up and running.
Has anyone had to migrate data from a windows base LMS 4.0 platform to a Solaris based LMS 4.0 platform?
ej

LMS 4.0 will not work on Solaris 9. Solaris 10 is the only supported Solaris version these days.

LMS 3.2 Installation - Solaris 10/09 Patch Conflict:

Hello all,
We are running Sun Solaris 10/09,working on installing LMS 3.2.As per documentation,attempted to install the two recommended patches,127127-11 and 122032-05.
The 127127-11 patch is already contained in this OS packaging.The second recommended patch - 122032-05 - does not install since there exists another patch - 141518-11 - that makes the second recommended patch(122032-05) obsolete.
The 141518-11 patch cannot be uninstalled since there is no backout data for it.
What do you recommend I do to solve this issue as I cannot move ahead with the installation as things stand.
Should I use an older release of Solaris 10 that is still downloadable from the Sun Website?If so,can anyone recommend a tried and tested release I can use.
Many thanks,
W.

Hi all,
Just resifted through the documentation and they have stated the supported releases:
"The following Solaris 10 releases are supported in LMS 3.2:
–Solaris 10, 05/09 release
–Solaris 10, 10/08 release
–Solaris 10, 05/08 release
–Solaris 10, 08/07 release
–Solaris 10, 11/06 release"
Will give the installation a shot with 10/08.
Regards,
W.

LMS 3.2 on Solaris 10 - Cannot tftp vlan.dat to server

Hi All,
I've read several posts and could not find one that would resolve my issue.
I get the partially successful on several switches. I understand that is because of LMS not being able to tftp vlan.dat back to server.
I tried it directly on a switch and the transfer only works if the filename is already created in the tftp directory. Is there a way to change that?
Thanks
Jose Ribeiro

Hi Joseph,
The ciscoworks server has full access to the switch as per below. Neither access nor credentials seem to be the issue here.
I've read a few posts where it was stated the need to create a 'dummy' vlan.dat file so that the device would not show as partially successful on the RME job. Is this the case here? If so this is a very strange solution.
Thanks,
Jose
-bash-3.00$ ssh [email protected]
[email protected]'s password:
CC
WARNING: This system is for authorized use only. Any or all access to or
uses of this system may be monitored and recorded and subject to audit.
Use of this system is expressed consent to such monitoring and recording.
Unauthorized or improper use of this system is prohibited and is subject
to criminal and civil penalties.
ctspotdcemsw302>ena
Password:
ctspotdcemsw302#
ctspotdcemsw302#sh ver
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-ENTSERVICESK9_WAN-M), Version 12.2(18)SXF1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Tue 20-Dec-05 19:11 by kellmill
Image text-base: 0x40101040, data-base: 0x42D60000
ROM: System Bootstrap, Version 12.2(17r)S2, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-ENTSERVICESK9_WAN-M), Version 12.2(18)SXF1, RELEASE SOFTWARE (fc1)
ctspotdcemsw302 uptime is 3 years, 28 weeks, 3 hours, 16 minutes
Time since ctspotdcemsw302 switched to active is 3 years, 28 weeks, 3 hours, 35 minutes
System returned to ROM by power cycle at 17:32:48 UTC Wed Jan 11 2006 (SP by power on)
System restarted at 05:35:07 EST Sun Feb 25 2007
System image file is "disk0:/s72033-entservicesk9_wan-mz.122-18.SXF1.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco WS-C6509-E (R7000) processor (revision 1.1) with 458720K/65536K bytes of memory.
Processor board ID SMG0832N2ZV
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from power-on
SuperLAT software (copyright 1990 by Meridian Technology Corp).
X.25 software, Version 3.0.0.
Bridging software.
TN3270 Emulation software.
15 Virtual Ethernet/IEEE 802.3 interfaces
266 Gigabit Ethernet/IEEE 802.3 interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
ctspotdcemsw302#exit
Connection to 10.86.109.3 closed by remote host.
Connection to 10.86.109.3 closed.
-bash-3.00$

LMS 3.2 on Solaris 10 - New devices and RME archive job

Hi All,
I've created a RME job that archive syncs our devices. When I add new devices to Common Services, which updates RME, will those new devices have their configurations archived by that same RME job, or do I need to create a new job?
When the existing job was created the option "All Devices" was selected.
Thanks,
Jose Ribeiro

Hi Jose,
If you really wants to track the devices configuration with the help of RME Jobs ( sometimes for auditing purpose we have to have a job ), then you can schedule a job as well but with the option Group Selector like (Select A Layer: Device SelectorGroup Selector ). You can see this option at the very top while creating the job. If you select this option, the membership of the group is dynamic in nature i.e this job will run on all those devices which exist in the group that you have selected at the time of running of job and not at the time of creation of job. For example, if you had created job on Normal Group of RME, then this job will attempt to take the backup of config of all those device which exist in Normal Group. So if your RME is synchronized with DCR (Common Services), and if you are adding the new device to Common Service, then you need not to add this device again for this schedule job since DCR will send this device to RME and once this device have inventory collected, it will automatically be in the normal group of RME and since we had selected Group selector option, RME will collect the config for this device too.
However periodic polling and periodic collection is also desinged to acheive the same purpose and known as kind of administrative task for managing the devices in RME.
Now the question arise what is difference between periodic polling and periodic collection :- Its very simple actually -
Periodic Polling :- Under Periodic polling, RME will first poll the device and if it find any change in the actual configuration of device with the existing configuration in RME . it will trigger collection of backup config for the device. If it will not find any difference between the actual configuration on the device and the existing configuration in RME, it will not trigger any new sync archive on the device thus save your network resources.
Periodic Collection :- Under Periodic Collection, it will not do any comparison and always trigger the sync archive on the device. However you will be able to see the new version of device configuration only when any change on the device happen since there is no point of keeping the same config many times in RME database.
Hope it answer your querries.
Thanks & Regards
Gaganjeet

LMS 3.2 on Solaris 10 - DFM 3.2 Shows VIP as Duplicate IP

Hi,
I have a few alerts created by DFM regarding duplicate ip addresses. It happens that those duplicate ips are in reality virtual ip addresses configured on our load balancers.
Is there a way to resolve this issue?
Thanks
Jose Ribeiro

This is a known issue (CSCee02681). The only workaround is to unmanage those IP addresses that are being reported as duplicates. This can be done under DFM > Device Management > Device Details. Expand the details tree, and select the IPs that are showing up as duplicates and set their management states to false.

LMS 3.2 on Solaris 10 - CatOS PVlan Mapping commands to MSFC not being saved by Ciscoworks

Hi All,
We are doing some troubleshooting after the recovery of a Cat6500 Hybrid switch and we've encoutered something strange. It seems that Ciscoworks does not save the pvlan mapping statements applied to the MSFC (module 15 in this case). Below I have two excerpts. The first one is from an export of the latest saved config of a similar device. The other one is from the actual same switch.
Any ideas why this is happening?
Thanks
Jose Ribeiro
-bash-3.00$ cat ctspitdcemsw303-172-raw.cfg | grep mapping
#Macro-Port mapping
#vlan mapping
set pvlan mapping 2100 2101 1/7
set pvlan mapping 2100 2103 1/7
set pvlan mapping 2100 2104 1/7
set pvlan mapping 2100 2106 1/7
set pvlan mapping 2100 2109 1/7
set pvlan mapping 2600 2603 5/11-12
set pvlan mapping 2600 2604 5/11-12
set pvlan mapping 2800 2801 5/4
set pvlan mapping 2800 2802 5/4
set pvlan mapping 2800 2803 5/4
set pvlan mapping 2800 2804 5/4
set pvlan mapping 2800 2805 5/4
set pvlan mapping 2800 2806 5/4
set pvlan mapping 2800 2807 5/4
set pvlan mapping 2800 2808 5/4
set pvlan mapping 2800 2809 5/4
set pvlan mapping 2300 2303 9/31
set pvlan mapping 2300 2304 9/31
set pvlan mapping 2600 2603 9/28
set pvlan mapping 2600 2604 9/28
-bash-3.00$
ctspitdcemsw303> (enable) sh runn | incl mapping
set pvlan mapping 2100 2101 1/7
set pvlan mapping 2100 2103 1/7
set pvlan mapping 2100 2104 1/7
set pvlan mapping 2100 2106 1/7
set pvlan mapping 2100 2109 1/7
set pvlan mapping 2600 2603 5/11-12
set pvlan mapping 2600 2604 5/11-12
set pvlan mapping 2800 2801 5/4
set pvlan mapping 2800 2802 5/4
set pvlan mapping 2800 2803 5/4
set pvlan mapping 2800 2804 5/4
set pvlan mapping 2800 2805 5/4
set pvlan mapping 2800 2806 5/4
set pvlan mapping 2800 2807 5/4
set pvlan mapping 2800 2808 5/4
set pvlan mapping 2800 2809 5/4
set pvlan mapping 2300 2303 9/31
set pvlan mapping 2300 2304 9/31
set pvlan mapping 2600 2603 9/28
set pvlan mapping 2600 2604 9/28
set pvlan mapping 2300 2303 10/35-36
set pvlan mapping 2300 2304 10/35-36
set pvlan mapping 2300 2305 10/35-36
set pvlan mapping 2300 2309 10/35-36
set pvlan mapping 2300 2303 11/34
set pvlan mapping 2300 2304 11/34
set pvlan mapping 2600 2603 11/12-13,11/38-39
set pvlan mapping 2600 2604 11/12-13,11/38-39
set pvlan mapping 2300 2303 12/45-46
set pvlan mapping 2300 2304 12/45-46
set pvlan mapping 2600 2603 12/41-44
set pvlan mapping 2600 2604 12/41-44
set pvlan mapping 2000 2001 15/1
set pvlan mapping 2000 2002 15/1
set pvlan mapping 2000 2003 15/1
set pvlan mapping 2000 2005 15/1
set pvlan mapping 2000 2009 15/1
set pvlan mapping 2200 2201 15/1
set pvlan mapping 2200 2202 15/1
set pvlan mapping 2200 2203 15/1
set pvlan mapping 2200 2208 15/1
set pvlan mapping 2300 2301 15/1
set pvlan mapping 2300 2302 15/1
set pvlan mapping 2300 2303 15/1
set pvlan mapping 2300 2304 15/1
set pvlan mapping 2300 2305 15/1
set pvlan mapping 2300 2306 15/1
set pvlan mapping 2300 2307 15/1
set pvlan mapping 2300 2309 15/1
set pvlan mapping 2300 2312 15/1
set pvlan mapping 2500 2501 15/1
set pvlan mapping 2500 2503 15/1
set pvlan mapping 2600 2602 15/1
ctspitdcemsw303> (enable)

Hi Joseph,
When I run a write term I can see the whole switch config, though in pages (I need to hit enter several time to go trhu the whole config).
ctspitdcemsw303> (enable) write terminal
This command shows non-default configurations only.
Use 'write terminal all' to show both default and non-default configurations.
begin
# ***** NON-DEFAULT CONFIGURATION *****
#time: Mon May 9 2011, 09:08:46 EDT
#version 8.5(2)
Also a View Config Raw from Device Center shows configuration up to module 10, completely missing modules 11, 12 and 15 (pvlan mappings to the MSFC).
Thanks,
Jose

LMS 3.2 (Solaris) db/backup problem

Hi team!
I have a LMS 3.2 on Solaris 10, and I have some problems after trying to install the last few DevicePackage:
1) several processes are not up, then I tried to restart DaemonManager from the console:
bash-3.00 # /etc/init.d/dmgtd stop
Daemon Management is not running.
INFO: Stopping DBEngine processes registered to Daemon Manager
WARNING: Daemon Manager could not stop DBEngine processes.
WARNING: Please run the command "/opt/CSCOpx/bin/dbstop.pl all"
WARNING: to stop DBEngine processes manually.
bash-3.00 # /opt/CSCOpx/bin/dbstop.pl all
Error retrieving dsns Can not open directory /opt/CSCOpx/backup/manifest;
bash-3.00 #
bash-3.00 # ps-ef | grep CSCOpx
casuser 28450 1 0 14:02:43? 3:04 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
casuser 28587 1 0 14:05:51? 13:38 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
casuser 28465 1 0 14:02:51? 1:27 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
casuser 28298 1 0 14:01:59? 30:15 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
    root 605 21740 0 17:37:32 pts / 1 0:00 grep CSCOpx
casuser 28319 1 0 14:02:23? 0:29 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
casuser 28439 1 0 14:02:35? 1:06 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
casuser 28309 1 0 14:02:19? 29:07 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
casuser 28361 1 0 14:02:31? 2:25 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
casuser 28480 1 0 14:02:59? 0:38 /opt/CSCOpx/objects/db/bin64/dbsrv10-x tcpip (HOST = localhost; DOBROADCAST = NO; Ser
bash-3.00 # kill -9 28450 28587 28465 28298 28319 28439 28309 28361 28480
bash-3.00 # ps-ef | grep CSCOpx
    root 607 21740 0 17:38:29 pts / 1 0:00 grep CSCOpx
bash-3.00 # /etc/init.d/dmgtd start
INFO: backed up /var/adm/CSCOpx/log/daemons.log to /var/adm/CSCOpx/log/daemonsbackup.log
Daemon Management 3.9 starting. Log = (syslog) /var/adm/CSCOpx/log/dmgtd.log
bash-3.00 #
2) SelfTest Information:
database.pl
WARN No Data Source Found, No Database Self Test is performed
3) Directory "manifest" - not exist (/opt/CSCOpx/backup/manifest).
How to fix the database?
How to rebuild the directory "manifest" (/opt/CSCOpx/backup/manifest)?
Can some one help me?

The result is negative:
bash-3.00#
bash-3.00# ls -la
total 10
drwxrwxr-x   5 casuser casusers     512 Oct 11 10:12 .
drwxrwxr-x 33 casuser casusers    1024 Oct 10 21:00 ..
drwxr-xr-x 11 casuser casusers     512 Oct 11 10:19 0
drwxr-xr-x 11 casuser casusers     512 Aug 27 02:33 11
drwxr-xr-x 11 casuser casusers     512 Sep 10 02:32 13
bash-3.00# /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -h -d /opt/CSCOpx/backup/
   Restore Program Help
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   To run the restore command, the command syntax is:
   /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl <-d BackupDirectory> [-gen GenerationNumber] [-t TempDirectory] [-help]
   BackupDirectory : Directory where the backup archive is present
   GenerationNumber: Generation to be restored
   TempDirectory   : Temporary directory for the restore program
                     Default TempDirectory for this restore program:
                     /opt/CSCOpx/tempBackupData
                     Use -t TempDirectory to define your own temp directory
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   Number of B/U generations kept are set on the 'Schedule Backup' HTML page.
   The most recent scheduled B/U generation will be that with the highest number.
   To restore a particular generation, use the command line option '-gen #'
   where # is a generation number from the list below.
   Generation 0 holds the most recent B/U executed from the 'Backup Data Now' page.
   To restore generation 0, use the '-gen now' parameter.
bash-3.00#
bash-3.00# /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d /opt/CSCOpx/backup/ -gen 11
Restore started at : 2010/10/11 10:38:57
Please see '/var/adm/CSCOpx/log/restorebackup.log' for status.
ERROR: Cannot find the generation in the backup directory [/opt/CSCOpx/backup/].
       Verify the backup directory and the generation
bash-3.00# /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d /opt/CSCOpx/backup/ -gen now
Restore started at : 2010/10/11 10:39:02
Please see '/var/adm/CSCOpx/log/restorebackup.log' for status.
ERROR: Cannot find the generation in the backup directory [/opt/CSCOpx/backup/].
       Verify the backup directory and the generation
bash-3.00# /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/restorebackup.pl -d /opt/CSCOpx/backup/ -gen 13
Restore started at : 2010/10/11 10:39:10
Please see '/var/adm/CSCOpx/log/restorebackup.log' for status.
ERROR: Cannot find the generation in the backup directory [/opt/CSCOpx/backup/].
       Verify the backup directory and the generation
bash-3.00#
I found directory "manifest" on the old server, it has been installed LMS 3.0 - can I use it? (current version of LMS 3.2)
There are still some methods or need to do to reinstall?

Prime Fulfillment 6 AND LMS 4.2 on single Solaris 10 server?

Is it possible to easily operate both Prime Fulfillment 6 AND LMS 4 on single Solaris 10 server?

They were not tested together, and I recommend they not be installed on the same zone instance (due to potential conflicts). Now, if you're certain you have a server that can accommodate both suites (in terms of resources), create separate zones for each suite. This will eliminate the conflict possibility while still giving you one overall physical machine to manage.

EPMServer processes don't die after dmgtd stop - LMS 4.2 Solaris

I am unable to kill EPMServer processes after shutting down LMS 4.2 on Solaris 10. There are still 60 or so EPMServer processes running. Killing them manually does not work as they appear to restart again after killing. Only way to knock them off is to reboot the system. Why does dmgtd stop not kill all LMS processes and is there a patch required for LMS 4.2 or Solaris 10 that would help?
EPMServer processes attached:
Thanks.

Any luck on resolving this problem? This is happening on multiple servers. Cannot kill EPMServer processes manually or by running .../etc/init.d/dmgtd stop to kill server. Killing processing directly will respawn same processes again. Only recourse is to reboot with these processes active.
: ps -ef|grep CSC
casuser 29811 29803   0 18:36:49 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
    root 18722 16794   0 10:32:21 pts/2       0:00 grep CSC
casuser   546     1   0   Aug 15 ?           0:00 /bin/bash /opt/CSCOpx/MDC/tomcat/webapps/rme/WEB-INF/compliancemgr/compliance/b
casuser 29803     1   0 18:36:34 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29808 29800   0 18:36:48 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29800     1   0 18:36:33 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29821 29811   0 18:37:05 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29817 29808   0 18:37:04 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29819 29810   0 18:37:05 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29790     1   0 18:35:37 ?           0:00 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29799     1   0 18:36:33 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29814 29805   0 18:36:51 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29839 29827   0 18:37:36 ?           0:00 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29810 29799   0 18:36:49 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29805     1   0 18:36:35 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29824 29814   0 18:37:09 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29827 29817   0 18:37:20 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29829 29819   0 18:37:21 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29831 29821   0 18:37:21 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29838 29829   0 18:37:36 ?           0:00 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29833 29824   0 18:37:24 ?           0:01 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29840 29831   0 18:37:37 ?           0:00 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5
casuser 29841 29833   0 18:37:40 ?           0:00 CSCO.EPMServer -Xms64M -Xmx1024m -cp:p conf/epm/patch:lib/classpath//cesar-v0-5

LMS 3.2 - Backup-Error -- ERROR(908): Cannot create or back up tar file

Hello again,
with performing backup (LMS 3.2 on Solaris 9) the following errors will arise.
dbbackup.log
/opt/CSCOpx/bin/tar: Removing leading `/' from absolute path names in the archive Apps file : /opt/CSCOpx/backup/manifest/upm/upminfo/datafiles.txt
[Tue Dec 8 08:56:54 2009] Archiving the contents of the following directories into /enbw/backup/files/cw_db_backup/0/upm/filebackup.tar
[Tue Dec 8 08:56:54 2009] /opt/CSCOpx/hum/conf/upm-snmp.properties
/opt/CSCOpx/hum/thresholdscript /opt/CSCOpx/MDC/tomcat/webapps/upm/reports
/opt/CSCOpx/MDC/tomcat/webapps/upm/WEB-INF/classes/com/cisco/nm/upm/properti
es/common/UPM.properties
/opt/CSCOpx/bin/tar: Removing leading `/' from absolute path names in the archive
/opt/CSCOpx/bin/tar: Cannot add file
/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/virt32841308_657_658_-718594975:
No such file or directory
/opt/CSCOpx/bin/tar: Cannot add file
/opt/CSCOpx/MDC/tomcat/webapps/upm/reports/virt32841308_658_659_1465769167:
No such file or directory
/opt/CSCOpx/bin/tar: Error exit delayed from previous errors [Tue Dec 8 09:07:30 2009] ERROR(908): Cannot create or back up tar file. Backup cancelled. Verify that you have write-access to this directory. [Tue Dec 8 09:07:30 2009] Backup failed: 2009/12/08 09:07:40 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Is seems to be problem related to maximal filesize handling of GNUtar implemented in CW2000.
The problem is with tar'ing HUM-Reports in /opt/CSCOpx/MDC/tomcat/webapps/upm/reports, and with reaching
tarfile-size of 2,9GByte error is thrown.
</exxx/backup/files/cw_db_backup/0/upm># ls -lh
total 6126448
-rw-r-----   1 casuser casusers    2.9G Dec 8 09:07 filebackup.tar
</exxx/backup/files/cw_db_backup/0/upm># ls -al
total 6126452
drwxr-x---   2 casuser casusers     512 Dec 7 14:30 .
drwxr-x--- 11 casuser casusers     512 Dec 7 14:30 ..
-rw-r-----   1 casuser casusers 3135201280 Dec 8 09:07 filebackup.tar
GNUtar-Version
# /opt/CSCOpx/bin/tar --version
tar (GNU tar) 1.13
Copyright (C) 1988, 92,93,94,95,96,97,98, 1999 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by John Gilmore and Jay Fenlason.
Is this a know problem?
Thanks for any thoughts.
Best Regards
Lothar

Hi Joe,
thanks for your feedback.
These files to be tarred aren't there directly after backup stops with error.
It seems that some process stores data about reports in that file and when trying to
pack these reports via tar they are delete by any cleanup method.
Does this help.
P.S. Backup usually takes about more than 1hour

Problems upgrading from LMS 3.0 to LMS 3.2 - the backup fails.

I'm upgrading from LMS 3.0 to LMS 3.2 on Solaris. I've met all of the prereq's, patches, etc. It keeps failing on the Backup...It claims I need 15 Gig for the backup. The backup directory I'm using (/opt/backup) has 35 Gig free, so that shouldn't be the issue.
Here is the error I'm seeing in the backup.log;
okcwsi:tail backup.log
tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis
co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi
gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c2950-i6q4l2-mz.121
-13.EA1c.bin: prefix is greater than 155
tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis
co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi
gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c1310-k9w7-tar.124-
10b.JDA2.tar: prefix is greater than 155
tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis
co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi
gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c2800nm-advsecurity
k9-mz.124-22.T1.bin: prefix is greater than 155
tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis
co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi
gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c3560-ipbase-mz.122
-53.SE2.bin: prefix is greater than 155
tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis
co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi
gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c7600-fpd-pkg.122-3
3.SRE1.pkg: prefix is greater than 155
tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis
co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_confi
gs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/c7600s72033-advente
rprisek9-mz.122-33.SRE1.bin: file name too long
tar: /var/adm/CSCOpx/files/rme/dcma/shadow/sw_images/cisco_configs/sw_images/cis
co_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/20100922075
156561-10.181.252.1.cfg: No such file or directory
ERROR(704): Cannot create or back up tar file. Backup cancelled. Verify that you
have write-access to this directory.
Backup failed: 2010/09/22 07:54:20
okcwsi:
I've tried this multiple times and each time it appears to fail on a different file/folder in the sw_images directory. This is our FTP directory where we store lots of IOS images for download. I've removed each of these files it errors out on and it keeps failing. I just removed all files from the sw_images folder and am trying the backup again now.
I'm attaching the backup.log which contains the failure information for each backup I've tried in the past two days.
My main question is...can I skip this backup somehow? I've got another LMS 3.0 system that I can export everything I need from. Skipping the backup isn't an option on the install/upgrade? It gives me the option to quit the install or try the backup again.
Thanks,

You can skip the backup with a hidden option:
./setup.sh -b nobackup
However, I wouldn't feel comfortable until figuring out why the backup has been failing, ostensibly because tar is running into the 255-char limit (100 for the filename and 155 for the path), a result of the many iterations of the following:
sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/cisco_configs/sw_images/

Logrot.pl (v.4.4) issue on solaris 9

logrot.pl does not check diskspace before doing a copy process of syslog_info; if there is not enough space, the copy process fails and the content of syslog_log is lost;
I know, that the error handling of such a script cannot take respect on each and every possible error that could appear but in case of the syslog file I would say it is such an essential file that it would be great that the loss of the content could be avoided.
currently I am unable to test if this issue is present in the current version but I found it to be valid in LMS 3.2 on solaris 9; here is the confiuration of logrot.pl
/var/log is configured as the backup directory,
/var/log/syslog_info is configured to be backed up
it seems when starting logrot.pl it first tries to copy syslog_info
the copy process fails due to /var being 100% in use
bash-2.05# /opt/CSCOpx/bin/logrot.pl -c
Read config successfully.
Logrot Configuration Menu
1. Edit variables
2. Edit log files
3. Quit and save changes
4. Quit without saving changes
Enter option: 1
Number Variable Name                    [Variable Value]
1.     Backup Directory                 [/var/log]
2.     Restart Delay                    [60]
q.     Go back
Enter variable number to change: q
Logrot Configuration Menu
1. Edit variables
2. Edit log files
3. Quit and save changes
4. Quit without saving changes
Enter option: 2
Number Logfile Name                     Number of Archives Max Size Compress
1.     /var/log/syslog_info             13                 1024     gz
a.     Add logfile(s)
d.     Delete logfile(s)
q.     Go back
Enter option or logfile number to edit: q
Logrot Configuration Menu
1. Edit variables
2. Edit log files
3. Quit and save changes
4. Quit without saving changes
Enter option: 4
bash-2.05#
===============================================================
===============================================================
bash-2.05# /opt/CSCOpx/bin/perl /opt/CSCOpx/bin/logrot.pl
cp: /var/log/syslog_info.12.gz: No space left on device
cp: /var/log/syslog_info.0: No space left on device
Wed Jun 8 16:44:03 2011: WARNING: Unable to archive /var/log/syslog_info: No such file or directory
gzip: /var/log/syslog_info.0: No such file or directory
Wed Jun 8 16:44:03 2011: WARNING: Unable to compress /var/log/syslog_info.0: 256
bash-2.05#
bash-2.05# cd /var/log/
bash-2.05# ls -al
total 769616
drwxr-xr-x   2 root     sys         1536 Jun 8 16:44 .
drwxr-xr-x 38 root     root        1024 Sep 24 2010 ..
-rw-------   1 root     sys            0 Jul 27 2005 authlog
-rw-r--r--   1 root     other     372880 Jun 8 02:00 cmMapShare.log
-rw-r--r--   1 root     other        838 Mar 22 2006 sysidconfig.log
-rw-r--r--   1 root     other        884 Jun 8 04:00 syslog
-rw-r--r--   1 root     other      17392 Jun 7 01:00 syslog.0
-rw-r--r--   1 root     other      17299 Jun 1 01:00 syslog.1
-rw-r--r--   1 root     other      16107 May 25 01:00 syslog.2
-rw-r--r--   1 root     other      15908 May 18 01:00 syslog.3
-rw-r--r--   1 root     other      16249 May 11 01:00 syslog.4
-rw-r--r--   1 root     other      17047 May 4 01:00 syslog.5
-rw-r--r--   1 root     other      15908 Apr 27 01:00 syslog.6
-rw-r--r--   1 root     other      15912 Apr 20 01:00 syslog.7
-rw-rw-r--   1 root     sys            0 Jun 8 16:44 syslog_info
-rw-rw-r--   1 root     sys      16485733 Sep 1 2010 syslog_info.0.gz
-rw-rw-r--   1 root     sys      16485733 Sep 1 2010 syslog_info.1.gz
-rw-rw-r--   1 root     sys      19319177 Dec 1 2009 syslog_info.10.gz
-rw-rw-r--   1 root     sys      87397723 Nov 3 2009 syslog_info.11.gz
-rw-rw-r--   1 root     sys      84321257 Oct 5 2007 syslog_info.2.Z.old
-rw-rw-r--   1 root     sys      20818106 Aug 1 2010 syslog_info.2.gz
-rw-rw-r--   1 root     sys      23242884 Jul 1 2010 syslog_info.3.gz
-rw-rw-r--   1 root     sys      19556306 Jun 1 2010 syslog_info.4.gz
-rw-rw-r--   1 root     sys      18299543 May 1 2010 syslog_info.5.gz
-rw-rw-r--   1 root     sys      21785629 Apr 1 2010 syslog_info.6.gz
-rw-rw-r--   1 root     sys      21120869 Mar 1 2010 syslog_info.7.gz
-rw-rw-r--   1 root     sys      23420015 Feb 1 2010 syslog_info.8.gz
-rw-rw-r--   1 root     sys      20852151 Jan 1 2010 syslog_info.9.gz
bash-2.05
before this action syslog_info was about 3 Gig

Would it be sufficient to change the warning about archival to an error to make it fatal?

LMS 3.2 in solaris

Similar Messages

Maybe you are looking for