LMS 3.2 customization

Unanswered Question
May 13th, 2010

Hi I have 18 sites of my company at different geographical areas. At each location I have to deploy LMS 3.2 in standalone mode. according to our company policies I have to customize LMS at every location. for example backup scheduling, purge scheduling, device discovery scheduling, config collection schedulling, dfm notification group creation etc.

At all location the server configurations will be identical i.e. server os, lms version and required policy.

is there any way by which I can replicate the LMS customizations to all installation instead of customizing LMS at every site?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
EmanuelArghittu Fri, 05/14/2010 - 02:44

hi mishra,

you could create a BackUP of the first site and use this for replicate the customization

create backup :

  

NMSROOT\bin\perl NMSROOT\bin\backup.pl BKP


where BKP is the backup directory.


You must enter the absolute path for BKP. For example, if BKP is under C:\, enter the path as NMSROOT\bin\perl NMSROOT\bin\backup.pl C:\BKP.

restore  backup:

net stop crmdmgtd

NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d BKP

where BKP is the backup directory.

You must enter the absolute path for BKP. For example, if BKP is under C:\, enter the path as NMSROOT\bin\perl NMSROOT\bin\restorebackup.pl -d C:\BKP


here are the log of restore:


E:\Progra~1\CSCOpx\log\restorebackup.log
E:\Progra~1\CSCOpx\log\rme_base.log
E:\Progra~1\CSCOpx\log\migration.log


after restore start daemon manager:

net start crmdmgtd
this procedure is to do backup of singol server or migration, so any data are replicated, also the ID of the server. this could be a problem for future use (master slave configuration), below the workeround:

in NMSROOT/lib/classpath/com/cisco/nm/dcr/dcr.ini this is the DCR ID that must be different fore any server, you could change the id if you need configure two or more of this servers in master/slave mode

ATTENTION!!

this is my solution, i don't know if is cisco raccomanded

I council you wait also the evaluation of another person

EmanuelArghittu Fri, 05/14/2010 - 03:08

sorry mishra,

in the .ini file you must verify also that DCR_GROUP_ID is unique

i'm sorry for the incomplete information

Satya Siba Sund... Sat, 05/15/2010 - 06:26

Hi Emanuel, restoring the backup only restores databases, syslogs, archieve files containing device run/start config, but not the settings like backup schedule, sync archieve schedule, dfm notification groups.

basicaly these configuration details are kept in " regdaemon.xml". but this file also contains the IP/hostname of existing installation which can't be change.

is there any other way??

Actions

This Discussion