|
|
ViewRunner Server applications can be configured through setting parameters in the $VRS_HOME/conf/vrconstants.conf file. The ViewRunner Client applications can be configured through setting parameters in the $VRC_HOME/conf/vrconstants.conf file. The server and client configuration files must match exactly. Mismatches between the files can cause unexpected behavior.
The following table details the parameters which can be set to configure the server and client applications. The following table contains information about each variable, including its name, description, range, default value, and unit (where applicable).
The ViewRunner server applications use all the parameters in the table, but the client applications use only the following parameters:
| Environment Variable Name | Description | Range | Default Value | Unit |
|---|---|---|---|---|
MAX_LOOPRUNNERS_PER_NETMON | Number of Cisco 6100s that are handled by a single View Network Monitor instance. If there are more than the specified value, multiple View Network Monitor applications will be started by View Process Monitor to manage the Cisco 6100s. The total number of View Network Monitors running should be limited to seven. Release 2.2 supports up to 300 Cisco 6100s. | 1- | 100 | Numeric |
SERVICE_HEARTBEAT_CHECK_TIMEOUT | The periodic polling interval for View Process Monitor to check the health of all other ViewRunner servers:
At this time-out, if any of the server instances are not running, View Process Monitor will restart the respective application. | 1- | 60 | seconds |
CLIENT_HEARTBEAT_CHECK_TIMEOUT | The periodic polling interval for the ViewRunner client to check if the connection to the ViewRunner server is healthy and re-connect if necessary. This value must be the same in both the remote client configuration file and the server configuration file. | 1- | 180 | seconds |
MAX_OPERATOR_LOGIN_RETRIES | Number of login attempts allowed for a ViewRunner user before disabling the user. If the number of consecutive login attempts that fail for the user exceeds the value of this parameter, the user will be disabled until a ViewRunner administrator re-enables the account. | 1- | 3 |
|
SNMP_TIMEOUT | The duration after which ViewRunner server will attempt to retransmit an SNMP request if the Cisco 6100 agent has not responded. This and SNMP_RETRIES will determine if communication with the agent has been lost. | 1- | 10 | seconds |
SNMP_RETRIES | Number of attempts ViewRunner server will send requests to the Cisco 6100 agent if a response has not been received within the specified SNMP_TIMEOUT interval. If the Cisco 6100 agent does not respond within this number of retries, ViewRunner will assert a LOSS_OF_COMMUNICATION alarm on the Cisco 6100. | 1- | 3 |
|
AUTO_DISCOVER_TIMEOUT | Periodic polling interval for ViewRunner servers to discover any new Cisco 6100s added to the network (to the topology database). This requires that IP Discovery be enabled in HP OpenView. | 1- | 1800 | seconds |
PERFORM_PERIODIC_SYNC | Enables or disables automatic periodic configuration synchronization of Cisco 6100s
It is preferable to do periodic syncs with a cron job rather than through the use of this variable. | 0 - 1 | 0 |
|
SYNCHRONIZE_TIMEOUT | Periodic polling interval for View Network Monitor to perform automatic configuration synchronization. This value is not used if PERFORM_PERIODIC_SYNC is 0. | 1- | 1800 | seconds |
COMMUNICATION_LOSS_TIMEOUT | Periodic polling interval for ViewNetMonitor to communicate with the agent with which communication is lost. | 1- | 120 | seconds |
PROCESSMON_HEARTBEAT_CHECK | Periodic polling interval when ViewRunner servers View Alarm Formatter, View Data Collector and View Network Monitor checks to see if View Process Monitor is running | 1- | 60 | seconds |
TRAP_INFO_RETRIEVAL_TIMEOUT | Periodic interval when View Alarm Formatter polls Cisco 6100 agents to verify the trap sequence number and the number of outstanding critical, major, and minor alarms | 1- | 120 | seconds |
ALARM_SYNC_CONFIRM_TIMEOUT | Interval at which ViewAlarm Formatter determines if it has missed any traps. It compares the sequence number of the last alarm received against the sequence number of the last trap delivered by the Cisco 6100. This interval is provided to ensure that "stuttering" alarms do not cause excessive equipment synchronizations. | 1- | 15 | seconds |
CLLI_CODE_SIZE | The size of Common Language Location Identifier (CLLI) code value for the Cisco 6100. Any CLLI code should not exceed this limit | 1-255 | 32 |
|
RELAY_RACK_INFO_SIZE | Defines the storage space for relay rack information for each Cisco 6100. | 1-255 | 32 |
|
AD_SNMP_TIMEOUT | Interval after which autodiscovery requests will be resent to the HP OpenView application ovtopmd if there is no response from OpenView | 1- | 10 |
|
AD_SNMP_RETRIES | Number of times auto discovery requests will be sent to OpenView application ovtopmd if there has been no response from OpenView | 1- | 1 |
|
SYNC_ON_OUT_OF_SYNC_DETECT | Enables or disables an automatic synchronization by View Network Monitor when configuration is detected to be out-of-sync between the Oracle database and a Cisco 6100.
| 0 - 1 | 1 |
|
NUM_FILES_SAVED_PER_LR | Defines the maximum number of NVRAM configuration files that will be saved per Cisco 6100 in the NSS directory for that Cisco 6100 $VRS_HOME/NSS/<IP Address of Cisco 6100>/ The directory will contain up to this many of the most recently saved NSS files. The oldest files will be deleted when this number is exceeded. | 1- | 5 |
|
DISPLAY_VIEWMAP_LOG_WINDOW | Specifies whether the View Map Log Window should be shown when View Map starts up. A user can open or close the window manually once View Map is running.
| 0-1 | 0 |
|
VIEWMAP_LOG_WINDOW_MAX_SIZE | Specifies the maximum number of lines to show in the View Map Log Window. | 1- | 500 |
|
VIEWMAP_LOG_WINDOW_SIZE | Specifies the initial number of lines to be used for the View Map Log Window. | 1- | 10 |
|
ADD_TIME_STAMP_TO_LOG_MESSAGE | Specifies whether the View Map log messages are to be time stamped.
| 0-1 | 1 |
|
DISABLE_INTELLIGENT_CONFIG_SYNC | Enables or disables intelligent configuration synchronization. Note If intelligent configuration synchronization is enabled, it is imperative that SYNC_ON_OUT_OF_SYNC_DETECT be enabled as well.
| 0-1 | 0 |
|
SET_REQUEST_SYNCHRONIZE_TIMEOUT | Specifies how often the servers update the database with the cached snmpInSetRequests value. | 1- | 300 | seconds |
MAX_GLOBAL_CONFIGURATION_SYNCS | Specifies the maximum number of configuration synchronizations that may be done across the entire ViewRunner for HP OpenView system simultaneously. | 1- | 15 |
|
MAX_CONFIGURATION_SYNCS_PER_NETMON | Specifies the maximum number of parallel configuration synchronizations that may be done by any single vrNetMon process. | 1- | 1 |
|
TFTP_TIMEOUT | Specifies the amount of time ViewRunner will wait for a TFTP transfer to complete. It does not set a timeout for the TFTP server. | 1- | 20 | minutes |
TRACE_FILE_MONITOR_TIMEOUT | Defines the time out for monitoring the trace file size. | 1- | 600 | seconds |
DEFAULT_UPSTREAM_MARGIN | Site configurable subscriber default upstream margin. | 0-12 | 6 | dB |
DEFAULT_DOWNSTREAM_MARGIN | Site configurable subscriber default downstream margin. | 0-12 | 3 | dB |
DEFAULT_UPSTREAM_RATE | Site configurable subscriber default upstream rates. See ViewRunner documentation for valid values. |
| 1080 |
|
DEFAULT_DOWNSTREAM_RATE | Site configurable subscriber default downstream rates. See ViewRunner documentation for valid values. |
| 7168 |
|
DEFAULT_TIMER_TYPE | Timer type site configurable default. | 1=none | 3 |
|
DEFAULT_TIMEOUT_VALUE | Site configurable subscriber defaults - timeout value | 1-240 | 100 | minutes |
SC_RESET_TIMEOUT | Specifies the timeout for SC reset and for clear provisioning, which invokes an SC reset. This is used in Software Download and in Restore Configuration. The SC may take a long time to reset if it is loading a new image. |
| 20 | minutes |
DELETE_NSS_AFTER_SWD | Specifies if the NSS file saved during Software Download should be deleted after the Software Download is complete. | 0=do not delete | 1 |
|
COMMUNICATION_SYNC_PER_MESSAGE_FREQUENCY | Determines the frequency at which a communication synchronization message will be sent between two processes communicating via a UNIX pipe. The parameter should be interpreted as for every <x> messages sent, the process will send 1 communication sync message. If the parameter is set to 0, the process will not send messages based on this rate. | 0=no sync message | 8 | number of messages sent |
COMMUNICATION_SYNC_TIME_FREQUENCY | Determines the time based rate which a communication synchronization message will be sent between two processes communicating via a UNIX pipe. The parameter should be interpreted as the process will send a communication sync message every <xx> seconds. If the parameter is set to 0, the process will not send the messages based on time. The time based rate has no effect during those intervals that have already sent a communication sync message based on the per message rate. | 0=no sync message | 20 | seconds |
DEFAULT_IDLE_TIMER_VALUE | Site configurable subscriber defaults - idle timer value. | 0-60 | 30 | minutes |
DEFAULT_SESSION_TIMER_VALUE | Site configurable subscriber defaults - session timer value. | 0-240 | 120 | minutes |
DEFAULT_LOCKOUT_TIMER_VALUE | Site configurable subscriber defaults - lockout timer value. | 0-60 | 20 | minutes |
DEFAULT_PVC_IDLE_MARK | Site configurable subscriber defaults - PVC idle mark. | 0-2147483647 | 1000 | PVCs |
DEFAULT_CPE_SIGNATURE_VALUE | Site configurable subscriber defaults - CPE signature. | 0=disable | 0 |
|
DEFAULT_ALLOW_136K_BAUD | Site configurable subscriber defaults - allow 136K baud. | 1=enable | 2 |
|
INBAND_MULTIPLIER_PERCENT | Specifies the percentage multiplier to be used for timeout calculation when communicating over inband channel. |
| 1000 |
|
CMF_FILE_NAME | Names the SC Feature Compatibility Matrix file. Default is SCFeatureCompatibilityMatrix.csv. |
| (see desc.) |
|
SERVER_DB_USER_NAME | Specifies the user name for database access by server applications. |
| vrunnerrw |
|
SERVER_DB_PASSWORD | Specifies the password for database access by server applications. |
| vrunnerrw |
|
CLIENT_DB_USER_NAME | Specifies the user name for database access by client applications. |
| vrunnerro |
|
CLIENT_DB_PASSWORD | Specifies the password for database access by client applications. |
| vrunnerro |
|
VR_ORACLE_TNS | Specifies the database connect string. |
| vrunner |
|
Posted: Fri Oct 8 12:40:33 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.