cc/td/doc/product/rtrmgmt/vpnsc/mpls/1_2
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Property Settings

Property Settings

The file csm.properties has the property setting information for MPLS VPN Solution. For each of the properties in the csm.properties file, Table B-2, "Property Information in csm.properties File," provides the default value, the range of values or the rules for valid values, and an explanation. You can use a text editor to reset the properties in the csm.properties file.

Note   Table B-1, "Reference for Server Information," provides a quick reference for where to get information about each of the servers. The properties in Table B-2, "Property Information in csm.properties File," are presented in the order they appear in the csm.properties file.

When entering a property, place a space, an equal sign, and another space after the property name and before the value you choose to assign. For example: netsys.datacollector.cct.sc_port = 1607

Many properties have the same prefix. In these cases, you will see the prefix to the far left and its subordinate properties indented.

The WatchDog and its Servers read this csm.properties file when started. Changing properties in this file and then stopping or restarting a single server does not necessarily have the desired effect. To be sure that the property changes are reflected in the running system, restart the entire system by running stopwd and then startwd.


Table B-1: Reference for Server Information
Server References Function

CNGSServer

Table B-2.

Provides a CORBA front end for the baseline management libraries.

CVPIMServer

Table B-2.

Provides a CORBA front end for provisioning and for downloading service requests.

DIPMServer

Table B-2.

Downloads router configuration files through the Cisco IP Manager product.

DataSetServer

Table B-2.

Provides a CORBA front end to the internal database.

EventGateway

Table B-2 and Table B-2.

Gateways events from the TIBCO domain to the CORBA domain.

LayoutServer

Table B-2.

Provides topology layout recomputation services for web topology, which is used when selecting certain topology views.

ReportServerFactory

Table B-2.

Launches and manages ReportServer processes that generate and provide access to dynamic web reports.

TaskServer

Table B-2.

Provides a CORBA front end to the MPLS VPN Solution task repository.

VerifyReportServer

Table B-2.

Back end that generates Verify Reports.

VpnInvServer

Table B-2.

Provisioning API CORBA server.

aggregator

Table B-2.

Aggregates collected datasets periodically.

httpd

Table B-2.

Web server.

journal

Table B-2

Listens to all repository events and saves them into journal files. Also archives the journal files periodically.

lock_manager

Table B-2.

Handles locking for the internal database.

log

Table B-2.

Makes the output of tasks available to you in a browsable format.

monitor

Table B-2.

Monitors events to provide user-level information.

poller

Table B-2.

Gets requests from other data collectors and forwards the requests to the device. Gets the response and sends it to appropriate collectors.

rmiregistry

Table B-2.

Underlying communication process necessary for ReportServerFactory and LayoutServer to communicate with web clients.

scheduler

Table B-2.

Enables you to schedule tasks immediately or later in time, once or several times.

trapcatcher (also referred to as: datacollector)

Table B-2; Table B-2.

Catches configuration change traps from routers.

watchdog_perf

Table B-2.

Tracks performance for the MPLS VPN Solution system itself. The data is collected and stored in the internal database only. The data is useful for diagnostics.


Table B-2: Property Information in csm.properties File
Property Default Value Range/
Rules 		Explanation

Router Settings:

netsys.router.

Login router and password prompts.

        loginprompt

Username:

Must match actual router prompts.

Login prompt.

        passwordprompt

Password:

Must match actual router prompts.

Password prompt.

trapcatcher Server:

netsys.datacollector.cct.

SmartCollector settings.

        sc_port

1607

>1024

The value is the port location at which the SmartCollector listens for traps.

        sc_delay

120

>0

The value is the number of seconds between writing traps to the repository.

        tc_targets

tc_targets

Valid filename.

This location is where all traps are kept. This file is for internal use.

        gc_targets

gc_targets

Valid filename.

This location is where all unused traps are kept.This file is for internal use.

        gc_failures

gc_failures

Valid filename.

This location is where all failed traps are kept. This file is for internal use.

        cycle_t

250

>0

The value is the number of minutes between full collections.

Miscellaneous System Settings:

netsys.tibco.service

7500

Integer port number or service name from /etc/service

Port number of TIB®/Rendezvous. During installation, you can change this default. For example, if you are running two copies of VPNSC on the same subnets, you must specify unique default values for each of these copies.

netsys.tibco.prefix

cisco.vpnsc.

Valid TIB®/Rendezvous subject.

Prefix for message subjects.

netsys.home.unix

<ECSP_HOME>

Valid directory name.

Home directory for MPLS VPN Solution.

netsys.RepositoryLocator.file.unix

<ECSP_HOME>/etc/rep.list

Valid complete file name.

Path for MPLS VPN Solution repository locator file.

netsys.tmpdir.unix

<ECSP_HOME>/tmp

Valid directory.

The location where scratch (temporary) files are kept.

netsys.expectdebug

2

0 means false; any nonzero integer means true.

For debugging purposes only. True turns on and false turns off debugging messages.

netsys.Debug

false

The valid values are: true and false.

For debugging purposes only. True turns on and false turns off debugging messages.

netsys.DebugVerbose

false

The valid values are: true and false.

For debugging purposes only. True turns on and false turns off verbose debugging messages.

netsys.vpnconsole.fullCheckOfServers

true

The valid values are: true and false.

The value true means the full server check occurs at startup.
The value false means the vpnconsole will skip the full server check at startup.

Note: The recommendation is to keep the default of true. If you choose false, this may result in erroneous behavior during the operation of vpnconsole, because some servers may not be in the started state.

For printing reports:

netsys.printer.unix

lp

netsys.html2ps.cmd.unix

<ECSP_HOME>/bin/\
execperldirect.sh \
<ECSP_HOME>/resources/\
htm12ps/htm12ps -f \
<ECSP_HOME>/resources/\
htm12ps/mpls.format

netsys.printer.cmd.unix

lpr

UNIX print command.

For log server, webserver, and browser support:

netsys.logSrv.addr.

Log server support.

        unix

<localhost>

Valid hostname.

Log server hostname.

        nt

<localhost>

Valid hostname.

Log server hostname.

netsys.WebServer.

Web server support.

        addr.unix

<localhost>:8080

Valid web server hostname and port.

Web server hostname and port.

        addr.nt

<localhost>:8080

Valid web server hostname and port.

Web server hostname and port.

        displayDebug

false

The valid values are: true and false.

For debugging purposes only. True turns on and false turns off debugging messages.

netsys.browser.unix

netscape

Default value only. Cannot be changed.

Browser support.

netsys.taskLogURL.unix

http://<localhost>:8080/servlet/
TaskLogs

Valid URL.

URL for viewing task logs.

netsys.ciscoURL.unix

http://www.cisco.com

Default value only. Cannot be changed.

Cisco URL.

netsys.deleteOldLogs

true

The valid values are: true and false.

True indicates to delete the task logs and false indicates not to delete the task logs.

netsys.retainLogsPeriod.unix

30

The valid values are:
7 to 365.

Indicates the number of days to keep the task log.

netsys.scheduler.

Scheduler threading control.

        maxThreads.unix

4

> 0

Defines the maximum number of worker threads to be created.

        maxWaitingThreads.unix

2

> 0

Defines the maximum number of worker threads to wait when there is no work to be done.

netsys.scheduler.scanTime

1

Any valid integer.

The scheduler scans the entire Repository every x number of minutes, where x is the number specified for this property.

netsys.cleanTempFiles

true

The valid values are: true and false.

The default true means that log files are deleted after they have been processed. False means that log files are not deleted after they have been processed.

netsys.ciscorouter.unix

The network, name, domain, and role are displayed in the network listing.

loginuser | loginpw | enableuser | enablepw

Use any of the following strings:

loginuser

loginpw

enableuser

enablepw

snmpro

snmprw

These target display fields are used to control what additional columns to display in the network window.

netsys.netflowhost.unix

The network, name, domain, and role are displayed in the network listing.

loginuser | loginpw | enableuser

Use any of the following strings:

loginuser

loginpw

enableuser

enablepw

snmpro

snmprw

These target display fields are used to control what additional columns to display in the network window.

Watchdog Settings:

netsys.watchdog.

        Debug

false

The valid values are: true and false.

For debugging purposes only. True turns on and false turns off global watchdog debugging messages The default is false.

        log.Debug

false

The valid values are: true and false.

For debugging only. True causes all logs to also appear to the WatchDog stdout. The default is false, which turns off stdout echoing.

        server.Debug

false

The valid values are: true and false.

For debugging only. False turns off and true turns on debugging messages related to servers only.

        heartbeat.Debug

false

The valid values are: true and false.

For debugging only. False turns off and true turns on debugging messages related to server heartbeats.

        servers

lock_manager
EventGateway
scheduler
monitor
httpd
DataSetServer
log
CVPIMServer
CNGSServer
trapcatcher
rmiregistry
ReportServerFactory
DIPMServer
poller
LayoutServer
VpnInvServer
VerifyReportServer
TaskServer
aggregator
watchdog_perf
journal

Server names as listed in Table B-1. Reference for Server Information

Specify the list of servers the WatchDog should create. Note: Each server can be configured individually using a set of properties prefixed with netsys.watchdog.\
server.\
<SERVER_NAME>

        group.repository_users

scheduler
httpd
DataSetServer
log
CVPIMServer
CNGSServer
ReportServerFactory
DIPMServer
LayoutServer
VpnInvServer
TaskServer
aggregator

Do NOT change. (Internal Use Only.)

Defines a group of Servers that use the repository. This allows the entire group to be started and stopped by using wdclient.

        heartbeat.period

120000

1000 - 86400000 (1 second - 24 hours)

Default period (in milliseconds) for server heartbeat detection.
Note: This setting is the default for all servers. This setting can be overridden for any specific server.

        heartbeat.timeout

15000

5000 - 600000
(5 seconds - 10 minutes)

Default timeout (in milliseconds) for server heartbeat detection.
Note: This setting is the default for all servers. This setting can be overridden for any specific server.

        heartbeat.start.delay

10000

0 - 60000
(0 seconds - 1 minute)

Amount of time (in milliseconds) to wait after executing a server and before attempting the first heartbeat.
Note: This setting is the default for all servers. This setting can be overridden for any specific server.

        start.timeout

120000

5000 - 600000
(5 seconds - 10 minutes)

Maximum time (in milliseconds) after a server is executed to restart a server that is not starting properly. After this time, the server is killed and restarted.
Note: If this value is less than the quick_die.threshold, there is an interaction with the quick_die properties.
Note: This setting is the default for all servers. This setting can be overridden for any specific server.

        quick_die.threshold

90000

30000 - 600000
(30 seconds - 10 minutes)

If a server does not stay running for at least the number of milliseconds specified in this parameter, it is considered to have died too quickly.
Note: This setting is the default for all servers. This setting can be overridden for any specific server.

        quick_die.count

3

1 - 10

If a server quickly dies the number of times specified in this parameter, it is disabled.
Note: This setting is the default for all servers. This setting can be overridden for any specific server.

        gentle_stop.timeout

10000

1000 - 30000
(1 second - 30 seconds)

This parameter specifies the number of milliseconds to wait after attempting a gentle stop before just killing the server anyway.
Note: This setting is the default for all servers. This setting can be overridden for any specific server.

        java.flags

None

Valid specification on the command line for the Java virtual machine.

This parameter specifies flags in addition to the default arguments that should be added to all Java servers launched by the watchdog.
Note: This setting is the default for all servers. This setting can be overridden for any specific server.

netsys.watchdog.server. \
<SERVER_NAME>.

        class

N/A. See each individual server for its default value.

A valid Java class name.

The Java class that represents the specified server within the watchdog.

        cmd

N/A. See each individual server for its default value.

A valid command line.

This command launches the server. If the command starts with the word "java", the watchdog rewords the command line to include a -DPROPERTY_FILE that matches the watchdog's property file and a -DOrbixWeb.config that matches the watchdog's property. In this situation, the command is the same for NT and UNIX.

        cmd.nt

None

A valid NT command line.

This specifies the command that launches the server for NT. Not used at this time.

        cmd.unix

None

A valid UNIX command line.

This specifies the command that launches the server for UNIX. Not used at this time.

        dependencies

None

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the specified server.

        putit

None

Valid CORBA Server names.

When this property is set, the watchdog ensures that the specified server is registered with the orb before this server is started.

        debug

false

The valid values are: true and false.

For debugging only. False turns off and true turns on debugging messages related to this server.

        quick_die.count

Same default as the watchdog's global quick_die.count value.

1 - 10

If the specified server dies quickly the number of times specified in this parameter, it is disabled.

        quick_die.threshold

Same default as the watchdog's global quick_die.threshold value.

30000 - 600000
(30 seconds - 10 minutes)

If the specified server does not stay running for at least the number of milliseconds specified in this parameter, it is considered to have died too quickly.

        start.timeout

Same default as the watchdog's global start.timeout value.

5000 - 600000
(5 seconds - 10 minutes)

Maximum time (in milliseconds) after the specified server is executed to restart a server that is not starting properly. After this time, the server is killed and restarted.

        heartbeat.timeout

Same default as the watchdog's global heartbeat.timeout value.

5000 - 600000
(5 seconds - 10 minutes)

Default timeout (in milliseconds) for detection of the specified server heartbeat.

        heartbeat.period

Same default as the watchdog's global heartbeat.period value.

1000 - 86400000 (1 second - 24 hours)

Default period (in milliseconds) for heartbeat detection of the specified server.

        heartbeat.start.delay

Same default as the watchdog's global heartbeat.start.delay value.

0 - 60000
(0 seconds - 1 minute)

Amount of time (in milliseconds) to wait after executing the specified server and before attempting the first heartbeat.

        gentle_stop.timeout

Same default as the watchdog's global gentle_stop.timeout value.

1000 - 30000
(1 second - 30 seconds)

If the specified server dies quickly the number of times specified in this parameter, it is disabled.

netsys.watchdog.server.watchdog_perf.

Watchdog performance monitor.

        class

netsys.NSWatchDog.servers. \
WDNoHeartbeat

Do NOT change. (Internal Use Only.)

The class that represents the watchdog performance server.

        cmd

watchdog_perf -period 60 \
-file_period 60

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch watchdog performance server.

        enable

false

The valid values are: true and false.

The value true indicates to generate data for performance monitor; the value false indicates not to generate data for performance monitor.

netsys.watchdog.server.EventGateway.

The EventGateway

        class

netsys.NSWatchDog.servers. \
WDEventGateway

Do NOT change. (Internal Use Only.)

The class that represents the EventGateway server.

        cmd

java netsys.event.gateway.\
EventGatewayImpl \
-state event_gateway.state \
-name EventGateway \
-ledger event_gateway.ledger \
-bind EventGateway

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch EventGateway server.

        putit

EventGateway

Do NOT change. (Internal Use Only.)

netsys.watchdog.server.httpd.

Web server

        class

netsys.NSWatchDog.servers. \
WDHttpd

Do NOT change. (Internal Use Only.)

The class that represents the httpd server.

        cmd

<ECSP_HOME>/resources/ \
webserver/\
JavaWebServer1.1.3/bin/nshttpd

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch httpd server.

        dependencies

lock_manager

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the httpd server.

        heartbeat.url

http://<localhost>:8080/

Valid web server URL.

The URL that is used for web server heartbeat testing.

        pidHint

httpd com.sun.server.\
ServerProcess

Do NOT change. (Internal Use Only.)

Used to find
the Web server process ID.

netsys.watchdog.server.lock_manager.

Lock manager

        class

netsys.NSWatchDog.servers. \
WDLockManager

Do NOT change. (Internal Use Only.)

The class that represents the lock_manager server.

        cmd

lm_ip -a <localhost>:12002 -u \
1000 -f 1000 -q 8000 -nd

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch lock_manager server.
Add: -l - to the end of the value to turn on debugging for lock manager.

        firstport

12000

Range of unused port numbers.

The lock manager port is changed by startwd to avoid problems when stopwd/startwd are run in quick succession.

        endport

12009

Range of unused port numbers.

The lock manager port is changed by startwd to avoid problems when stopwd/startwd are run in quick succession.

        restart.delay

15000

>0

The lock manager port is changed by startwd to avoid problems when stopwd/startwd are run in quick succession.

        heartbeat.start.delay

30000

>0

Amount of time (in milliseconds) to wait after executing the lock_manager server and before attempting the first heartbeat.

netsys.watchdog.server.trapcatcher.

Trap receiver

        class

netsys.NSWatchDog.servers. \
WDTrapCatcher

Do NOT change. (Internal Use Only.)

The class that represents the trapcatcher server.

        cmd

java netsys.datacollector.\
cct.Traps

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch trapcatcher server.

netsys.watchdog.server.scheduler.

The scheduler

        class

netsys.NSWatchDog.servers. \
WDScheduler

Do NOT change. (Internal Use Only.)

The class that represents the scheduler server.

        cmd

java -mx64m \
netsys.SCH.netsys_scheduler

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch scheduler server.

        dependencies

lock_manager monitor poller

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the scheduler server.

netsys.watchdog.server.monitor.

The monitor

        class

netsys.NSWatchDog.servers. \
WDMonitor

Do NOT change. (Internal Use Only.)

The class that represents the monitor server.

        cmd

java netsys.TRT.Monitor

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch monitor server.

        dependencies

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the monitor server.

netsys.watchdog.server.DataSetServer.

The DataSetServer

        class

netsys.NSWatchDog.servers. \
WDDataSetServer

Do NOT change. (Internal Use Only.)

The class that represents the DataSetServer server.

        cmd

java -mx64m \
netsys.datacollection.\
datasetserver.DataSetServer

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch DataSetServer server.

        dependencies

lock_manager

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the DataSetServer server.

        putit

DataSetServer

Do NOT change. (Internal Use Only.)

        start.timeout

300000

>0

netsys.watchdog.server.log.

The log server

        class

netsys.NSWatchDog.servers. \
WDLog

Do NOT change. (Internal Use Only.)

The class that represents the log server.

        cmd

java netsys.logmonitor.logSrv. \
logmonitor.LogServer

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch log server.

        dependencies

lock_manager

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the log server.

        putit

log

Do NOT change. (Internal Use Only.)

When this property is set, the watchdog ensures that the log server is registered with the orb before it is started.

netsys.watchdog.server. \
CVPIMServer.

VPN Provisioning and Inventory Manager process.

        class

netsys.NSWatchDog.servers. \
WDCVPIMServer

Do NOT change. (Internal Use Only.)

Name of the Java class used by the WatchDog to poll CVPIMServer's heartbeats.

        cmd

CVPIMServer -dlthreads 10

Can ONLY change values in command options. Otherwise, make no changes.

Use this command line option to set the number of threads to be started for uploading configuration files from routers and for downloading configlets to routers. The only valid option is -verbose, which instructs CVPIMServer to print out debugging messages.

        dependencies

lock_manager

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent server lock_manager is started before the CVPIMServer server.

        putit

CVPIMServer

Do NOT change. (Internal Use Only.)

Name of CVPIMServer as registered with the Orbix daemon.

        maxroutepercent

80

        frameRelayLmiType

none

Valid choices are:

ansi
cisco
q933a
none (no specification of LMI type allowed)

Local Management Interface (LMI) type selection.

        uploadConfig

true

The valid values are: true and false.

True indicates that the provisioning server uploads a copy of the configuration file from the routers when it processes the Service Request, and false indicates that the provisioning server does not do this uploading but instead uses copies of the configuration files that were previously collected and stored in the Repository.

        maxRetries

0

Any valid integer.

Maximum number of download retries (automatic retry occurs the specified number of times if the retryInterval property is also set). Note: If the number of Service Requests in Requested or FailedDeploy state drops to zero before the maxRetries limit is reached, the retries terminate at that time.

        retryInterval

0

Any valid integer.

Elapsed time (sleep time in seconds) between download retries (automatic retry occurs in the specified time interval if the maxRetries property is also set).

netsys.watchdog.server. \
CNGSServer.

The CNGS server CORBA interface for access to MPLS data by external applications.

        class

netsys.NSWatchDog.servers. \
WDCNGSServer

Do NOT change. (Internal Use Only.)

The class that represents the CNGSServer server.

        cmd

CNGSServer -serverName \
CNGSServer -htmlDirectory \
<ECSP_HOME>/tmp\
-persistent

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch CNGSServer server.

        dependencies

lock_manager

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the CNGSServer server.

        putit

CNGSServer

Do NOT change. (Internal Use Only.)

When this property is set, the watchdog ensures that the CNGSServer server is registered with the orb before it is started.

netsys.watchdog.server. \
rmiregistry.

Java RMI Registry

        class

netsys.NSWatchDog.servers. \
WDNoHeartbeat

Do NOT change. (Internal Use Only.)

The class that represents the rmiregistry server.

        cmd

java \
sun.rmi.registry.RegistryImpl

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch rmiregistry server.

        dependencies

None

Do NOT change. (Internal Use Only.)

When this property is set, the watchdog ensures that the CNGSServer server is registered with the orb before it is started.

netsys.watchdog.server. \
LayoutServer.

Java RMI Registry

        class

netsys.NSWatchDog.servers. \
WDLayoutServer

Do NOT change. (Internal Use Only.)

The class that represents the LayoutServer server.

        cmd

java -Djava.rmi.server.codebase\
=http://<localhost>/Baselines/ \
topology.layout.\
CSRMILayoutServerImp \
LayoutServer

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch LayoutServer server.

        dependencies

rmiregistry httpd

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the LayoutServer server.

netsys.watchdog.server. \
ReportServerFactory.

The Report Server Factory

        class

netsys.NSWatchDog.servers. \
WDReportServerFactory

Do NOT change. (Internal Use Only.)

The class that represents the ReportServerFactory server.

        cmd

java netsys.csm.\
CSMReportServerFactory

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch ReportServerFactory server.

        dependencies

lock_manager rmiregistry \
DataSetServer

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the ReportServerFactory server.

netsys.watchdog.server. \
poller.

The Poller

        class

netsys.NSWatchDog.servers. \
WDPoller

Do NOT change. (Internal Use Only.)

The class that represents the poller server.

        cmd

java netsys.datacollector. \
mibdatacollection.ServerCorba

Can ONLY change values in command options. Otherwise, make no changes

Command to launch poller server.

        putit

mibpoller

Do NOT change. (Internal Use Only.)

When this property is set, the watchdog ensures that the poller server is registered with the orb before it is started.

netsys.watchdog.server. \
VpnInvServer.

CORBA interface to VpnInventory Repository

        class

netsys.NSWatchDog.servers. \
WDVpnInvServer

Do NOT change. (Internal Use Only.)

The class that represents the VpnInvServer server.

        cmd

VpnInvServer -v

The default value with and without -v are the only valid values.

Command to launch VpnInvServer server.

If you want to turn off the verbose mode, remove the -v option.

        dependencies

lock_manager

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the VpnInvServer server.

        putit

VpnInvServer

Do NOT change. (Internal Use Only.)

When this property is set, the watchdog ensures that the VpnInvServer server is registered with the orb before it is started.

netsys.watchdog.server. \
TaskServer.

CORBA interface to Task Repository

        class

netsys.NSWatchDog.servers. \
WDTaskServer

Do NOT change. (Internal Use Only.)

The class that represents the TaskServer server.

        cmd

TaskServer -v

The default value with and without -v are the only valid values.

Command to launch TaskServer server.

If you want to turn off the verbose mode, remove the -v option.

        dependencies

lock_manager

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the TaskServer server.

        putit

TaskServer

Do NOT change. (Internal Use Only.)

When this property is set, the watchdog ensures that the TaskServer server is registered with the orb before it is started.

netsys.watchdog.server. \
aggregator.

Dataset Aggregator

        class

netsys.NSWatchDog.servers. \
WDAggregator

Do NOT change. (Internal Use Only.)

The class that represents the aggregator server.

        cmd

java netsys.datacollector. \
aggregator.Aggregator

Do NOT change. (Internal Use Only.)

Command to launch aggregator server.

        dependencies

lock_manager poller

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the aggregator server.

        SLA.interval

120

>0

Maximum interval (number of minutes) between two consecutive SA Agent aggregation operations.

        ACCT.interval

240

>0

Maximum interval (number of minutes) between two consecutive accounting aggregation operations.

netsys.watchdog.server. \
journal.

The journal Server for Repository events.

        class

netsys.NSWatchDog.servers.\
WDJournal

Do NOT change. (Internal Use Only.)

The class that represents the journal server.

        cmd

java netsys.repository.journal.\
receiver.JournalListener

Do NOT change. (Internal Use Only.)

Command to launch journal server.

        dependencies

lock_manager

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the journal server.

        aging

24

>0

Number of hours the journal server will back up current journal files.

        archiving

7

>0

The number specified indicates the number of days between occurrences when the journal server will create an archive directory for journal files. For example, for the default of 7, the journal will create an archive directory for journal files every 7 days.

netsys.watchdog.server. \
VerifyReportServer.

The VerifyReportServer generates verify reports.

        class

netsys.NSWatchDog.servers. \
WDVerifyReportServer

Do NOT change. (Internal Use Only.)

The class that represents the VerifyReportServer server.

        cmd

java netsys.datacollection.\
datasetmanagers.\
DCDSMVerifyMgr.sdf.\
RemoteVerifyReportServer

Can ONLY change values in command options. Otherwise, make no changes.

Command to launch VerifyReportServer server.

If you do not want the verbose mode, remove the -v option.

        dependencies

DataSetServer lock_manager \
rmiregistry

Do NOT change. (Internal Use Only.)

Watchdog ensures that the dependent servers are started before the VerifyReportServer server.

netsys.watchdog.

Configuration for e-mail notification when servers restart

        email.host

No default.

Set during installation.

This parameter specifies the hostname of the SMTP connection for sending e-mail. If this parameter remains blank, the machine name that watchdog is launched from is the hostname used.

        email.from

No default.

Set during installation.

This parameter indicates what is specified in the From: header in the e-mail.

        email.server

No default.

Set during installation.

This parameter specifies a list of users who are notified when the state of servers changes.

        email.stable_seconds

60000

>0

This parameter specifies the amount of time (in milliseconds) that the state of the servers must remain stable before an e-mail is generated.

        disks.high

20%

0 - 100% or
0 - <maximum capacity of volume>M

Maximum value of free disk space before e-mail message is sent to address indicated by netsys.watchdog.email.disk

        disks.low

10%

0 - 100% or
0- <maximum capacity of volume>M

Minimum value of free disk space before e-mail message is sent to address indicated by netsys.watchdog.email.disk

        email.disk

No default.

Any valid e-mail address.

The user to which to send e-mail when free disk space rises above the netsys.watchdog.disks.\
high level or drops below the netsys.watchdog.disks.\
low level.

MediatorPerfLog related properties:

netsys.mediatorPerfLog.

MediatorPerfLog related properties

        jvmStatusPeriod

60000

10000 - 86400000
(10 seconds - 24 hours)

This parameter specifies the default interval (in milliseconds) for server jvmStatus log entries.

        logFileDuration

300000

300000 - 86400000 (5 minutes - 24 hours)

This parameter specifies the default interval (in milliseconds) for creating new server log files.

MibDataCollector related properties:

mibdatacollector.chassisinfofile.

MibDataCollector related properties.

        unix

<ECSP_HOME>/etc/\
chassis_info.txt

Valid filename.

        nt

<ECSP_HOME>\etc\
chassis_info.txt

Valid filename.

Poller related properties:

poller.

Poller related properties.

        SC.Enabled.unix

no

        SC.Enabled.nt

no

        debuglevel.unix

1

        debuglevel.nt

1

        maxThreads.unix

5

>0

Maximum number of threads spawned by poller on UNIX.

        maxThreads.nt

5

>0

Maximum number of threads spawned by poller on NT.

DIPMServer related properties:

netsys.watchdog.server.DIPMServer.

DIPMServer related properties.

        class

netsys.NSWatchDog.servers. \
WDDIPMServer

Do NOT change. (Internal Use Only.)

The class that represents the DIPMServer server.

        cmd

DIPMServer -serverName DIPMServer -properties\
<ECSP_HOME>/etc/\
csm.properties -persistent

Can ONLY change values in command options. Otherwise, make no changes

Command to launch DIPMServer server.

        putit

DIPMServer

Do NOT change. (Internal Use Only.)

When this property is set, the watchdog ensures that the DIPMServer server is registered with the orb before it is started.

DIPMServer.

DIPMServer modes for provisioning.

        mode

ECHO

CIPM
IPM

ECHO uses the repository to get router configurations to simulate download, read the configuration from the repository, and return it with the configlets appended on the end.
CIPM or IPM uses Cisco IP Manager to upload and download router configurations.

        debugLevel

2

The valid values are:

1; 2; and 3.

The value of 1 means no debug output.
The value of 2 means verbose output.
The value of 3 means full (very verbose) debug output.

        threadCount

10

The valid values are: 1 to 20.

The value indicates the number of threads the DIPMServer will use for get configuration and download requests. Each thread handles one request. The value should be the same as the thread count in the netsys.watchdog.server.CVPIMServer.cmd property.

        CIPMDomainParentName

Root

All domains created will be subdomains of this domain.

        CIPMNameServer

None

If the Cisco IP Manager was installed specifying a domain, the hostnames must have the domain appended.

        CIPMPrimaryNEMServer

None

To be used for all domains created by DIPMServer in CIPM.

        CIPMBackupNEMServer

None

Not supported at this time.

        CIPMErrorMapFile

<ECSP_HOME>/etc/PSError\Map.properties

List of error strings for the error codes returned by the Cisco IP Manager.

        CIPMCopyRunningToStartup

true

The valid values are: true and false.

The values of true means the running config will be copied to start up after downloading configlets.

        CIPMTransferModeOnCreate

telnet

The valid values are: telnet and tftp.

When an element is created in Cisco IP Manager, the transfer mode is set to this value.

        CIPMIOSWarningExpressions

^% Unknown VPN

^%IP routing table VRF.* does not exist. Create first$

^%No CEF interface information

^%No matching route to delete$

^%Not all config may be removed and may reappear after reactivating

Patterns that match IOS Warning messages.

These expressions are used to detect IOS warning messages. CIPM cannot distinguish between errors and warnings because both begin with `%'. The CIPM response buffer is checked. Any line that begins with `^%' is checked for the first pattern that matches one of the valid expressions. If none of the lines gets to that point, an error is returned.

        CIPMIOSErrorExpressions

^Must remove RED configuration first.

^Bad mask /[0-9]+ for address

^Not a valid address

Patterns that match IOS Error messages.

Uses the specified regular expressions to detect IOS errors that do not begin with a `%' and therefore are not marked by CIPM as errors. The CIPM response buffer is checked against these expressions and an error is returned if any line matches one of these expressions.

Note: The first pattern that matches the expression is considered a match. The entire line does not need to be a match.

netsys.vpn.ServiceRequest.\
showTemplates

false

The valid values are: true and false.

The value true indicates to enable the template steps used by the Service Request wizard.

The value false indicates to disable the template steps used by the Service Request wizard.

Configure the data set server:

netsys.datasetserver.

Configuring the data set server.

        managers

Directory Baseline\
RouteTableIP \
RouterConfig SlaBrowser CCT \
Acct VFIT Verify MediatorPerf

Do NOT change. (Internal Use Only.)

The data set managers that are to be started by DataSetServer.

        manager.Directory.class

netsys.datacollection.\
DCDirectory. \
DirectoryManagerImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.Baseline.class

netsys.datacollection. \
datasetmanagers. \
DCDSMBaselineMgr. \
BaselineManager Imp1

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.RouteTableIP.class

netsys.datacollection. \
datasetmanagers. \
DCDSMRouteTableIPMgr. \
RouteTableIPManagerImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.RouterConfig.class

netsys.datacollection. \
datasetmanagers. \
DCDSMRouterConfigMgr. \
RouterConfigManagerImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.SlaBrowser.class

netsys.sla.CiscoSlaMonitor. \
SlaBrowserImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.CCT.class

netsys.datacollection. \
datasetmanagers. \
DCDSMCCTMgr.\
CCTManagerImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.Acct.class

netsys.acct.CiscoAcctMonitor. \
AcctMonitorImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.VFIT.class

netsys.datacollection. \
datasetmanagers.\
DCDSMVFITMgr.\
VFITManagerImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.Verify.class

netsys.datacollection. \
datasetmanagers.\
DCDSMVerifyMgr.\
VerifyManagerImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

        manager.MediatorPerf.class

netsys.datacollection. \
datasetmanagers. \
DCDSMMediatorPerfMgr. \
MediatorPerfManagerImpl

Do NOT change. (Internal Use Only.)

Classes that implement each data set manager.

Cell color properties in Accounting reports:

netsys.datasetserver.manager.Acct.

These properties control the color schemes of the following reports:

-CE2CECustomer\
TrafficVolume is a CE-CE Customer Traffic Volume Report.

-PE2PENetwork\
TrafficVolume is a PE-PE Network Traffic Volume Report.

-PE2CETraffic Volume is a PE-CE Traffic Volume Report.

A valid time period is:

-hourly

-daily

-weekly

-monthly

-yearly

A valid measure is:

-packets

-bytes (in K bytes)

A valid color property is one of the following:

-white -lightgray

-gray -darkgray

-black -blue

-cyan -green

-magenta -orange

-pink -red

-yellow

These properties are used to specify cell colors in Accounting reports. The range properties and color properties go in pairs to define a color scheme. New ranges can be added. You can also specify range3 and color3; range4 and color4 The reports display different colors depending on the value in the cells.

The property names all start with netsys.datasetserver.\manager.Acct followed by all of the following:

- a report name

- a time period

- a measure

- a range or color. The range and color numbers must be a matching pair. For example, for range1 there must be a color1. The number of pairs is unlimited. However, the range and color numbers must start from 1 and be in consecutive integer order.

The range property is a number range (which is inclusive). The range must be two numbers separated by a space, or substitute a number with a dash to indicate there is no lower or upper limit.

Customer Traffic Volume Report (CE-CE):

        CE2CECustomerTrafficVolume. \
hourly.packets.range1

5000 49999

        CE2CECustomerTrafficVolume. \
hourly.packets.color1

yellow

        CE2CECustomerTrafficVolume. \
hourly.packets.range2

50000 -

        CE2CECustomerTrafficVolume. \
hourly.packets.color2

red

        CE2CECustomerTrafficVolume. \
hourly.bytes.range1

5000000 49999999

        CE2CECustomerTrafficVolume. \
hourly.bytes.color1

yellow

        CE2CECustomerTrafficVolume. \
hourly.bytes.range2

50000000 -

        CE2CECustomerTrafficVolume. \
hourly.bytes.color2

red

        CE2CECustomerTrafficVolume. \
daily.packets.range1

120000 1199999

        CE2CECustomerTrafficVolume. \
daily.packets.color1

yellow

        CE2CECustomerTrafficVolume. \
daily.packets.range2

1200000 -

        CE2CECustomerTrafficVolume. \
daily.packets.color2

red

        CE2CECustomerTrafficVolume. \
daily.bytes.range1

120000000 1199999999

        CE2CECustomerTrafficVolume. \
daily.bytes.color1

yellow

        CE2CECustomerTrafficVolume. \
daily.bytes.range2

1200000000 -

        CE2CECustomerTrafficVolume. \
daily.bytes.color2

red

        CE2CECustomerTrafficVolume. \
weekly.packets.range1

840000 8399999

        CE2CECustomerTrafficVolume. \
weekly.packets.color1

yellow

        CE2CECustomerTrafficVolume. \
weekly.packets.range2

8400000 -

        CE2CECustomerTrafficVolume. \
weekly.packets.color2

red

        CE2CECustomerTrafficVolume. \
weekly.bytes.range1

840000000 8399999999

        CE2CECustomerTrafficVolume. \
weekly.bytes.color1

yellow

        CE2CECustomerTrafficVolume. \
weekly.bytes.range2

8400000000 -

        CE2CECustomerTrafficVolume. \
weekly.bytes.color2

red

        CE2CECustomerTrafficVolume. \
monthly.packets.range1

3600000 35999999

        CE2CECustomerTrafficVolume. \
monthly.packets.color1

yellow

        CE2CECustomerTrafficVolume. \
monthly.packets.range2

36000000 -

        CE2CECustomerTrafficVolume. \
monthly.packets.color2

red

        CE2CECustomerTrafficVolume. \
monthly.bytes.range1

3600000000 35999999999

        CE2CECustomerTrafficVolume. \
monthly.bytes.color1

yellow

        CE2CECustomerTrafficVolume. \
monthly.bytes.range2

36000000000 -

        CE2CECustomerTrafficVolume. \
monthly.bytes.color2

red

        CE2CECustomerTrafficVolume. \
yearly.packets.range1

43200000 431999999

        CE2CECustomerTrafficVolume. \
yearly.packets.color1

yellow

        CE2CECustomerTrafficVolume. \
yearly.packets.range2

432000000 -

        CE2CECustomerTrafficVolume. \
yearly.packets.color2

red

        CE2CECustomerTrafficVolume. \
yearly.bytes.range1

43200000000 431999999999

        CE2CECustomerTrafficVolume. \
yearly.bytes.color1

yellow

        CE2CECustomerTrafficVolume. \
yearly.bytes.range2

432000000000-

        CE2CECustomerTrafficVolume. \
yearly.bytes.color2

red

Network Traffic Volume Report (PE-PE):

        PE2PENetworkTrafficVolume. \
hourly.packets.range1

5000 49999

        PE2PENetworkTrafficVolume. \
hourly.packets.color1

yellow

        PE2PENetworkTrafficVolume. \
hourly.packets.range2

50000 -

        PE2PENetworkTrafficVolume. \
hourly.packets.color2

red

        PE2PENetworkTrafficVolume. \
hourly.bytes.range1

5000000 49999999

        PE2PENetworkTrafficVolume. \
hourly.bytes.color1

yellow

        PE2PENetworkTrafficVolume. \
hourly.bytes.range2

50000000 -

        PE2PENetworkTrafficVolume. \
hourly.bytes.color2

red

        PE2PENetworkTrafficVolume. \
daily.packets.range1

120000 1199999

        PE2PENetworkTrafficVolume. \
daily.packets.color1

yellow

        PE2PENetworkTrafficVolume. \
daily.packets.range2

1200000 -

        PE2PENetworkTrafficVolume. \
daily.packets.color2

red

        PE2PENetworkTrafficVolume. \
daily.bytes.range1

120000000 1199999999

        PE2PENetworkTrafficVolume. \
daily.bytes.color1

yellow

        PE2PENetworkTrafficVolume. \
daily.bytes.range2

1200000000 -

        PE2PENetworkTrafficVolume. \
daily.bytes.color2

red

        PE2PENetworkTrafficVolume. \
weekly.packets.range1

840000 8399999

        PE2PENetworkTrafficVolume. \
weekly.packets.color1

yellow

        PE2PENetworkTrafficVolume. \
weekly.packets.range2

8400000 -

        PE2PENetworkTrafficVolume. \
weekly.packets.color2

red

        PE2PENetworkTrafficVolume. \
weekly.bytes.range1

840000000 8399999999

        PE2PENetworkTrafficVolume. \
weekly.bytes.color1

yellow

        PE2PENetworkTrafficVolume. \
weekly.bytes.range2

8400000000 -

        PE2PENetworkTrafficVolume. \
weekly.bytes.color2

red

        PE2PENetworkTrafficVolume. \
monthly.packets.range1

3600000 35999999

        PE2PENetworkTrafficVolume. \
monthly.packets.color1

yellow

        PE2PENetworkTrafficVolume. \
monthly.packets.range2

36000000 -

        PE2PENetworkTrafficVolume. \
monthly.packets.color2

red

        PE2PENetworkTrafficVolume. \
monthly.bytes.range1

3600000000 35999999999

        PE2PENetworkTrafficVolume. \
monthly.bytes.color1

yellow

        PE2PENetworkTrafficVolume. \
monthly.bytes.range2

36000000000 -

        PE2PENetworkTrafficVolume. \
monthly.bytes.color2

red

        PE2PENetworkTrafficVolume. \
yearly.packets.range1

43200000 431999999

        PE2PENetworkTrafficVolume. \
yearly.packets.color1

yellow

        PE2PENetworkTrafficVolume. \
yearly.packets.range2

432000000 -

        PE2PENetworkTrafficVolume. \
yearly.packets.color2

red

        PE2PENetworkTrafficVolume. \
yearly.bytes.range1

43200000000 431999999999

        PE2PENetworkTrafficVolume. \
yearly.bytes.color1

yellow

        PE2PENetworkTrafficVolume. \
yearly.bytes.range2

432000000000 -

        PE2PENetworkTrafficVolume. \
yearly.bytes.color2

red

Traffic Volume Report (PE-CE):

        PE2CETrafficVolume. \
hourly.packets.range1

5000 49999

        PE2CETrafficVolume. \
hourly.packets.color1

yellow

        PE2CETrafficVolume. \
hourly.packets.range2

50000 -

        PE2CETrafficVolume. \
hourly.packets.color2

red

        PE2CETrafficVolume. \
hourly.bytes.range1

5000000 49999999

        PE2CETrafficVolume. \
hourly.bytes.color1

yellow

        PE2CETrafficVolume. \
hourly.bytes.range2

50000000 -

        PE2CETrafficVolume. \
hourly.bytes.color2

red

        PE2CETrafficVolume. \
daily.packets.range1

120000 1199999

        PE2CETrafficVolume. \
daily.packets.color1

yellow

        PE2CETrafficVolume. \
daily.packets.range2

1200000 -

        PE2CETrafficVolume. \
daily.packets.color2

red

        PE2CETrafficVolume. \
daily.bytes.range1

120000000 1199999999

        PE2CETrafficVolume. \
daily.bytes.color1

yellow

        PE2CETrafficVolume. \
daily.bytes.range2

1200000000 -

        PE2CETrafficVolume. \
daily.bytes.color2

red

        PE2CETrafficVolume. \
weekly.packets.range1

840000 8399999

        PE2CETrafficVolume. \
weekly.packets.color1

yellow

        PE2CETrafficVolume. \
weekly.packets.range2

8400000 -

        PE2CETrafficVolume. \
weekly.packets.color2

red

        PE2CETrafficVolume. \
weekly.bytes.range1

840000000 8399999999

        PE2CETrafficVolume. \
weekly.bytes.color1

yellow

        PE2CETrafficVolume. \
weekly.bytes.range2

8400000000 -

        PE2CETrafficVolume. \
weekly.bytes.color2

red

        PE2CETrafficVolume. \
monthly.packets.range1

3600000 35999999

        PE2CETrafficVolume. \
monthly.packets.color1

yellow

        PE2CETrafficVolume. \
monthly.packets.range2

36000000 -

        PE2CETrafficVolume. \
monthly.packets.color2

red

        PE2CETrafficVolume. \
monthly.bytes.range1

3600000000 35999999999

        PE2CETrafficVolume. \
monthly.bytes.color1

yellow

        PE2CETrafficVolume. \
monthly.bytes.range2

36000000000 -

        PE2CETrafficVolume. \
monthly.bytes.color2

red

        PE2CETrafficVolume. \
yearly.packets.range1

43200000 431999999

        PE2CETrafficVolume. \
yearly.packets.color1

yellow

        PE2CETrafficVolume. \
yearly.packets.range2

432000000 -

        PE2CETrafficVolume. \
yearly.packets.color2

red

        PE2CETrafficVolume. \
yearly.bytes.range1

43200000000 431999999999

        PE2CETrafficVolume. \
yearly.bytes.color1

yellow

        PE2CETrafficVolume. \
yearly.bytes.range2

432000000000-

        PE2CETrafficVolume. \
yearly.bytes.color2

red

netsys.srvc.VRFRDOverride.unix

false

The valid values are:

true, which allows manual modification of VRF and RD;
false, which does not allow manual modification of VRF and RD.

Manual modification of VRF and RD

netsys.passwd.file.unix

<ECSP_HOME>/etc/\
passwordFile

Any valid filename.

Location of the password file to log into the VPN Console.

netsys.htpasswd.unix

<APACHE_HOME>/bin/\
htpasswd

Valid location of an htpasswd executable.

Absolute path to the htpasswd executable, which is part of the Apache web-server package.

netsys.access.logfile.unix

vpnUserAccess.log

Any valid filename.

Filename where the VPN Console access history is stored. If the filename is not an absolute path, the file is stored in the temporary directory, specified by the property netsys.tmpdir.unix.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Thu Sep 21 12:05:39 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.