Command
|
Description
|
dbpasswd.pl
|
Changes a database's password along with its access configuration files.
dbpasswd.pl {all | dsn=data source [opwd=old password]
[pfile=properties file] | listdsn}
|
restorebackup.pl
|
Restores an earlier backup of the database.
/opt/CSCOpx/bin/perl restorebackup.pl [-force]
[-s groupName] [-gen generationNumber]
{-d backup directory}
This script can be used for user-specific requirements to:
• Restore only one group. For this, use the '-s groupName' parameter.
•Restore all groups. For this, do not use the '-s' parameter.
•Installed suites that includes CMF and Essentials.
•See a list of the available backed-up generations. For this use the following command line:
/opt/CSCOpx/bin/perl restorebackup.pl -h
{-d backup directory}
|
backup.pl
|
Backs up the database.
/opt/CSCOpx/bin/perl backup.pl backdir [logfilename [numberGen] ]
|
dmgtd
|
Process manager daemon. Specify the tcp port to use the Daemon Management protocol on. All clients will need to have the env var PX_DMGTHOST and env var set. Daemon Manager Protocol enabled applications can report additional status. Daemon Manager sends status information to Syslog (facility: LOG_DAEMON).
dmgtd [ -p port -v] [ names ]
|
dig
|
Sends domain name query packets to name servers. Dig (domain information groper) is a flexible command line tool which can be used to gather information from the Domain Name System servers. Dig has two modes:
•Simple interactive mode which makes a single query
•Batch which executes a query for each in a list of several query lines.
All query options are accessible from the command line.
dig [@server] domain [query-type] [query-class]
[+query-option] [-dig-option] [%comment]
|
bg2rigel.pl
|
Imports data manually from Essentials 2.2 or earlier. If you are upgrading from Essentials 3.1 or 3.2 to version 3.3, you do not need to change the format of your data or import data manually. You might need to import manually if:
•You have installed Essentials 3.3 but have data from Essentials 2.2 or earlier that is installed on a different system.
•You have upgraded from Essentials 2.2 or an earlier version to version 3.3 but there was not enough disk space to convert and import the older version's saved data in the default location.
where path is the path name of the directory in which the older Essentials data resides.
If you had any errors during importing the data, check the log file
located at /var/adm/CSCOpx/log/bg2rigel.log. The Technical
Assistance Center (TAC) might ask you to send them the log file.
|
uninstall.sh
|
Uninstallation program that removes files and settings. Uninstallation allows you to remove only Essentials or remove CiscoWorks2000 CD One as well. To remove CD One, you must remove Essentials as well. Before removing Essentials, you must first remove any applications that depend on Essentials.
|
RmeJobCreateService.pl
|
Creates new jobs from exported RME job data into Coyote system.
Exported job data will be read from NMSROOT/rigel backup directory.
Script will disable all the jobs after creation.
|
RmeJobEnableService.pl
|
Enables all the jobs disabled by Coyote upgrade or Job creation service.Information about list of jobs to be enabled is obtained from joblist.jrm and rmedisabledjobs.jrm under NMSROOT/setup directory.
|
removeJrmJobs.pl
|
Removes all the existing JRM jobs from cmf database. This is used in
remote upgrade.
|
removeRmeJobs.pl
|
Deletes all the Job Information from RME database. This is used in
remote upgrade.
|
import_rme.pl
|
Restores RME files required for remote upgrade from rigel to Coyote.
|
cwconfig
|
CiscoWorks2000 command line tool that allows you to access the
configuration archive or configurations on devices. You can use
cwconfig to update, export, and import configurations on devices and
in the archive. You can also compare configurations and delete old
configurations. To get a list of supported commands, run the command:
Help on each command can be obtained as:
For example:
Additionally, man pages are available on UNIX installations for individual commands. To view the man page for any command, enter:
|
SampleEmailScript.pl
|
Wrapper around the OS specific mail program. Accepts the usual parameters like sender, subject, email_ids, text_message and sends the message to the intended recipient.
sampleEmailScript.pl -email_ids list of comma separated email
addresses, -subject [subject of email] optional -from [from who]
-sender [sender] -smtp [SMTP, needed for NT], -text_message
[message text, '\n' character is used to break up message into multiple
lines]
|
crmimport
|
Script used for CRM device data import. The crmimport command is a command line utility for the Resource Manager Essentials which is used to import device information from CiscoWorks(tm), CiscoWorks for Switched Internetworks(tm), HP OpenView(tm), Castlerock's SNMPc(tm) (on Windows NT only), or any other source of devices that can export lists of devices and their passwords. crmimport is similar to CRM's function Admin > Inventory > Import from File.
Unix environment:
rmimport.pl [-o | -d] importFile
Windows NT environment
crmimport.cmd [-o | -d] importFile
|
cwinvcreport
|
CiscoWorks2000 command line interface for the Inventory Custom Reports. cwinvcreport allows you to run the previously created Inventory Custom Reports. The output is displayed in (CSV) Comma separated value format. You can re-direct the output to an e-mail recipient or to a file.
The log and the output files are created in the current directory. The report name should be given within double quotes.
cwinvcreport [-d debuglevel] [-m email] [-l logfile]
[-o outputfile] "reportname"
You could enable debug mode and set the debug using the -d option. You could mail the output to an e-mail recipient using the -m option. You could log the error messages to a file using the -o option.
•To display the list of existing reports, specify the -r option.
•To display cwinvcreport version information, specify the -v option.
•To display the usage information, specify the -h option.
|
pdexec / pdshow / pdterm
|
Controls process manager.
pdshow/pdexec/pdterm [ appName1 appName2 ... ]
•To get status of registered processes appName1, appName2, ..., send a request to CRM process manager using the command:
pdshow [appName1 appName2 ...]
•To start the registered process appName1 if it is not running, send a request to CRM process manager using the command:
•To stop the registered application appName1 if it is running send a request to CRM process manager using the command:
•pdshow will show the status of all processes registered if no arguments are given.
•pdexec and pdterm require one or more appNames.
where appNameN represents the registered name of each process that is
registered with CRM process manager.
|
pdmsg
|
Broadcasts a string to all registered daemons under Daemon Management that are in the "Running Normally" state.
To use this command, Daemon Management server must be running.
|
pdreg
|
Registers and unregisters applications with CRM Process Manager.
pdreg [-r appName -e pgm [-f pgmFlags ] [-d dependencies ]
[-n] [-t 0|p|n ] ] | [-u appName ] | [-l appName ]
•To register a process and invoke it without the -n or -t option.
appName must be 25 alphanumeric characters or less.
•To unregister a process and shut it down if the process is running.
•To list the registry for a particular daemon.
|
pdrun.pl
|
Wrapper to run a command-line instruction with the CW2000 environments.
The command line instruction to be run has to be double quoted as the argument. If the command-line instruction itself contains double quotes, proceed it with a back slash.
To run a command line instruction with the CW2000 environments
perl pdrun "pdshow \"ANIServer jrm\""
|
