13.2.1 ConfigurationThe configuration of the servers and the WEB user interface is performed with the editing of the CONFIG_INI.PM file in the etc directory. The editable sections are enclosed between the “#ALLITHATOAK KEZDET” and “#ALLITHATOAK VEG” strings. It is recommended to prepare the configuration file only once and copy it to the other machines. The possible forms of string parameters are: $[parameter name]='[parameter value]'; or $[parameter name]{category name}{subparameter name }='[parameter value]'; or $[parameter name]{category name}='[parameter value]'; The form of toggle parameters is: $[parameter name]=[0 or 1]; The obligatory parameters that must always be set are typed in bold face, while parameters required for subsequent tuning or for larger installations are typed underlined or in italic, respectively. The default values of those parameters not marked with any of the above methods are suitable in most cases. The individual parameters and their meanings: · USER: the name of the Oracle user · PWD: the password of the Oracle user. PVSR can store the password in an encrypted way. To convert a clear text password to an encrypted one, use the show_encrypted_pwd.pl command in the bin directory. The script does not modify the CONFIG_INI.pm! · TNS: Oracle TNS · ORACLE_HOST: the host name of the Oracle machine · ORACLE_PORT: the port number of the Oracle listener, typically 1521 · ORACLE_SERVICE_NAME or ORACLE_SID: the name of the Oracle database service · ORACLE_HOME: the Oracle HOME directory · APACHE_HOME: the Apache HOME directory. The application uses this parameter to find the htpasswd program, it expects that in the APACHE_HOME/bin directory · PVSR_HOME: The root directory of the application · DISPLAY_CUSTOMER_NAME: If it is set to 1 then PVSR shows the customer name from the license file on the WEB GUI next to the version number · JAVA_HOME: The root directory of the JAVA program, the application looks for the java command in the JAVA/bin directory · FM_URL: the URL for NETvisor’s Fault Manager application UI. PVSR can show a Fault Manager Operation entry for equipments an measurements, opening the same object in Fault Manager, but only if the NETINV_UDA parameter is set and the object has a value specified by that parameter · NETINV_UDA: the name code for the user defined attributes holding the NETinv identifier for the object · IPE_URL and IPE_PARAMETER_NAME: the URL for NETvisor’s IPExplorer application UI. PVSR can show an IPExplorer Operation entry for equipments, opening the same object in IPExplorer. If IPE_PARAMETER_NAME is set to “ipAddress” then the link generated by PVSR will try to look up the equipment using its IP address. Otherwise it will try to look up the equipment using its name · REST_ENABLE_REALTIME: the real-time monitoring is only enabled through the REST API (which is used by the mobile app) if the value of this parameter is set to 1 · PVSR_FORKS (has category and subparameter too): The number of programs making the measurements of the equipment, this configuration can be specified individually for each of the measurement servers (the category, which is the ID of the measurement server or the “default” string, the later of which cannot be omitted) and measurement cycles (the subparameter, which is the possible measurement cycles in seconds or the “default” string, the later of which cannot be omitted). This value must be tuned according to the number of equipment, their interfaces, and their access time. The measurement applications primarily search for the configuration with their own ID. If no such found, then they take the default category. After that they search for the subparameter corresponding to the cycle. Therefore, using the configuration below the measurement server with ID 100 for the 300-second cycle will choose the value of 4 for this parameter: $PVSR_FORKS{default}{300}=50; $PVSR_FORKS{100}{default}=4; · PVSR_REDISCOVERY_FORKS (has category): The configuration of equipment is executed by this many separately running measurement programs, if this value is set. If this value is not specified, then the system uses 1 as the default value. The category values are also the server IDs or the default string. This value must be tuned according to the number of equipment, their interfaces, and their access time. · PVSR_JOB_FORKS: the number of job queue processing programs · INTERVAL_PVSR_SNMPOPTIONS (has category and subparameter): Contains the default parameters of the SNMP and other active measurements: if the parameter is specified for a piece of equipment, then that values is used everywhere. On the other hand, if the parameter is not specified at the equipment level, then the value specified here is used that correspond to the default measurement frequency for the discovery queries, and to the measurement frequency for measurements. The names of the individual categories correspond to the possible measurement intervals in seconds. If the parameter is not specified for some measurement interval, then the value specified for default category is used. The subparameters are: o timeout: SNMP or other timeout in seconds. Its value is 2 if not set o retries: the number of tries to perform the access (that is number 2 means one retry). If not set, then the default value is 5 o version (only for SNMP): SNMP version · REQUIRED_SUCCESSFUL_MEASUREMENTS (has category and subparameter): the category is the server ID and the subparameter is the collection interval. The data loader checks for each collector / collection interval pair the number of successful measurements and if its is smaller than the value specified by this parameter then it raises an alarm. The value of the parameter is either an integer or a percentage. In the later case the alarm is raised if less then the specified percentage of measurements is successful. I.e. the initial value “85%” means that the system generates an alarm if less then 85% of the measurements for any collector server / collection interval are successful. · SERVER_COLLECTION_TOO_LOW_ERROR_INTERVALS (has category and subparameter): the category is the server ID and the subparameter is the collection interval. When there are not enough successful measurements (see previous parameter) then PVSR sends out an error only after this many collection cycles. The default value is 2 · REQUIRED_ACK_COMMENT_LENGTH: if set to a number then users can only acknowledge/unacknowledge alarms if they provide a comment at least this long · MAX_EQS_PER_SITE: if set then PVSR will only display the given number of equipments at once under any site on the Alarm, Measurement and Site and equipment configuration page. If there are more equipments then PVSR will display a page able table · DISABLE_ONDEMAND_AUTO_VIRT_SITE_RESYNCH: if set to 1 then PVSR will not synchronize the automatic virtual sites after each modification in the system. Instead only a regular automatic virtualization will take place every five minutes · THRESHOLD_DEDUP_WINDOW and EVENT_DEDUP_WINDOW: the default deduplication windows can be specified with these parameters · DEF_RETAIN_RAW_DATA: The default number of days offered to retain measurement data · PVSR_BULK_SNMP: The application can group the measurements data on each piece of equipment to minimize the number of SNMP messages during data collection. This number of measurements are grouped together if this parameter is specified (a measurement is considered a piece of data to which one chart is displayed, that is, for example the input and output traffic together constitute one measurement). If the equipment is measured by SNMPv1 and any of the queried SNMP variables does not exist, then all measurements in the packet will be unsuccessful · PVSR_BULK_WALK_SNMP: If an equipment is of SNMPv2c or SNMPv3 type and the value set here is larger than 1, then PVSR quires this many variables together with the help of BulkWalk · DELETE_DAILY_DATA_AFTER: The number of days before the old measurement data will be deleted (see the server module operation cycle descriptions for more detail). · VIOLATION_DELETE_AFTER: The number of month after which the system will delete old alarms · REPORT_DELETE_AFTER: The number of month after which the system will delete old report values · AUDIT_TRAIL_DELETE_AFTER: The number of month after which the system will delete old audit trail records · SMTP_SERVER: The server to which the application sends the emails. · ADMIN_EMAIL_ADDRESSES: a list of email addresses separated with commas, to which the system sends sever event notifications. After each email address there can be two optional parts. One specifies the server event levels for which PVSR should send a notification. Each level is identified by a character: o I: information o W: warning o E: error o C: clear They must be placed between [ and ] characters. If the other option is present then PVSR only sends maximum one summary notification daily (if there are events at all) and the option must be in the format <HH:MM> where the HH:MM specifies the time when the summary should be sent. Example: my.address@gmail.com[EC],other@gmail.com[EWC]<03:00>,another@gmail.com · ADMIN_SNMP_TRAP_ADDRESSES: a list of IP addresses separated with commas, to which the system sends an SNMP trap if the status of some of the servers has changed, or some other server event has occurred. Optionally the port and the community can be specified as well, so the value “1.2.3.4” is the same as “public@1.2.3.4:162” · PVSR_EMAIL_ADDRESS: that email address can be specified which is used as the sender for outgoing email messages. If it is not specified, then it is automatically set to PVSRprogram@<hostname>, while if the specified value does not contain the @ sign, then the <specified value>@<hostname> is used · PVSR_THRESHOLD_EMAIL_ADDRESS: if this is set then PVSR will send out the threshold violations using this source address instead of the PVSR_EMAIL_ADDRESS · PVSR_WEB_EMAIL_ADDRESS: if this is set then PVSR will send out the WEB server emails (“Send as an email” operations) using this source address instead of the PVSR_EMAIL_ADDRESS · PVSR_REPORT_EMAIL_ADDRESS: if this is set then PVSR will send out the reports using this source address instead of the PVSR_EMAIL_ADDRESS · APPL_MAN_SEPARATE_VIRT_SITE_PROCESS: if set to 1 then the Application Manager module will start a separate child process to handle the automatic virtual site synchronization. It is recommended to set the parameter if there are several automatic virtual sites in the system · APPL_MAN_SEPARATE_STATUS_CHECK_PROCESS: if set to 1 then the Application Manager module will start a separate child process to handle the module status checking and so these won’t be handled in the same process as the other tests (like Oracle connectivity) and file maintenances. It is recommended to set the parameter if there are several modules and their availability is not reliable and so their status can change frequently · THRESHOLD_AUTO_CREATE_CYCLE: the template bases automatic threshold process cycle in hours · SQLLDR_ASYNC_LDR_MODE: the parameter governs whether the SQLLDR module’s data processing is synchronous or not. The parameter has four possible values: o 0 (default): the module downloads the measurement result files one-by-one and then loads them into the database o 1: the module downloads the measurement result files one-by-one but while loading them into the database it keeps looking for new result files and keeps downloading them o 2: the module forks new processes and downloads the measurement result files parallel and then loads them into the database o 3: the module forks new processes and downloads the measurement result files in parallel and while loading them into the database it keeps creating new processes and keeps downloading the result files parallel · ENABLE_MEASUREMENT_LEVEL_RIGHTS: measurement level rights can only be granted to users if it is set to 1, otherwise only equipment and site level rights can be granted · PROC_THRESH_QE_SOCKET_BUFFER_SIZE: if it is set then the quick evaluation threshold processing module changes the receiver socket buffer size to this value. It is only recommended to set this parameter if the module receives the values over UDP · QUICK_EVAL_THRESHOLD_SSL_CERT_FILE: if the quick evaluation threshold processing module receives the data over SSL then this parameter must contain the name of the certificate file which must be in the PVSR’s etc directory · QUICK_EVAL_THRESHOLD_SSL_KEY_FILE: if the quick evaluation threshold processing module receives the data over SSL then this parameter must contain the name of the key file which must be in the PVSR’s etc directory · QUICK_EVAL_THRESHOLD_SSL_PASSWORD: if the quick evaluation threshold processing module receives the data over SSL and the key file is password protected then this parameter must contain the password · QUICK_EVAL_THRESHOLD_SSL_NO_VERIFY: if the quick evaluation threshold processing module receives the data over SSL and this parameter is set to 1 then the certification won’t be verified · SNMP_ENABLE_IP_ADDRESS_FOR_NON_ADMINS: if this is set to 1 then the normal users are also allowed to view the IP address of SNMP equipments · DISABLE_TIMEZONES: if this is set to 1 then the time zone feature will be disabled · DISABLE_BUSINESS_HOURS: if this set to 1 then the business hours feature will be disabled · MTIME… parameters: The application manager zips and deletes on each machine running PVSR the old log and other files. The files to be processed are searched for using the find operating system command. The values for the following parameters are used with the mtime argument when running the find command: o MTIME_FOR_LOG_FILE_ZIP: log file zipping, default: 1 o MTIME_FOR_LOG_FILE_ZIP_DELETE: deletion of the zipped log files, default: 14 o MTIME_FOR_SQLLDR_FILE_ZIP: SQLLDR log and data file zipping, default: 0 o MTIME_FOR_SQLLDR_FILE_ZIP_DELETE: deletion of the zipped SQLLDR log and data files, default: 2 o MTIME_FOR_CHART_FILE_DELETE: deletion of the generated chart files, default: 7 · VIEW_MERES_YEAR: Should the chart be displayed for the current year on the page of the measurement. The possible values are: o 0: The chart is not displayed o 1: The chart is displayed o 2: Only a link is displayed, when it is clicked on the page is reloaded and the chart is displayed. · VIEW_MERES_MONTH: Should the chart be displayed for the current month on the page of the measurement. The possible values are: o 0: The chart is not displayed o 1: The chart is displayed o 2: Only a link is displayed, when it is clicked on the page is reloaded and the chart is displayed. · VIEW_MERES_WEEK: Should the chart be displayed for the current week on the page of the measurement. The possible values are: o 0: The chart is not displayed o 1: The chart is displayed o 2: Only a link is displayed, when it is clicked on the page is reloaded and the chart is displayed. · IF_CHECK_CIKLUS: The equipment configurations are queried with this period of many measurement cycles. The equipment configurations are queried by the basic measurement cycle, that is, if its value is 3, then the first, second and third thirds of the set of equipment are processed one after the other, in 3 basic measurement cycles total. · DISABLE_IFSPEED_CHECKING: If its value is 1 then the interface traffic won’t be displayed if its value is greater than the 150% of the interface speed. It its value is 2 then the speed checking is completely disabled, meaning that the received value from the equipment won’t be disregarded even if the interface new traffic counter value is smaller than the previous one and the calculated traffic is greater than 150% of the interface speed (see the server module operation cycle descriptions for more detail). · DEF_DRAW: The default image to be displayed · SMTP_AUTH: If set, then its format is “user/password”, which is used to login to the SMTP server. · PVSR_REDISCOVERY_MAXWAIT: The maximum number of seconds used by the application for each equipment to read its configuration settings in case of rediscovery · ZERO_NO_VALUE: If its value is 1, then missing measurement data is regarded as a zero value, otherwise it is the last measured value · MAXX_PER_MAXY: The X and Y axis lengths ratio for the generated charts; the width of the internet browser window determines the length of the X axis · MIN_MAXY: The minimum length of the Y axis for the generated charts, the height of charts will be this value if the calculated value is smaller then this one · USE_PARTITONS: see the section 5.7 · DONT_MOVE_PARTITION_TO_ARCHIV: see the section 5.7 · CREATE_PP_TABLE_AFTER: see the section 5.7 · DROP_DATA_AFTER: see the section 5.7 · USE_DIRECT_SQLLOADER: This parameter used only when the application employs a partitioned database. If the number of measurement results is greater than or equal to this number during a single measurement cycle, then the SQL*Loader Oracle application will be used directly to load the data. The recommended value is 40000 · USE_SORT_FOR_UNIQUE_MERGE: If it is set to 1 then the SQLLDR module will sort the data file content and it will eliminate any duplicated rows in the data file. This requires additional memory on the server side and it is only recommended if there is at least one server group which has more than one collector server · REGATHER_FORK_SLEEP: Is specified, the system waits this many seconds before starting the process to rediscover each additional pieces of equipment (run_regather). Its value can be fractional as well. · COLLECT_FORK_SLEEP: If specified, the system waits this many seconds before starting each individual measurement process (run_measurement). Its value can be fractional as well. · MOVE_MON_RES: The number of days or hours before measurement data is moved to the archive table (see the server module operation cycle descriptions for more detail). · SSH_TIMEOUT: The timeout of SSH connections in seconds. By SSH connection in this case we mean a connection from the application manager and WEB interface to the machines running the other servers (management and equipment information queries), and SFTP connections between the SQLLDR data loader and measurement servers · APPLMAN_CLOSE_SSH_AFTER_TEST: if it is set to 1 then the Application manager closes the SSH connections to the other servers after each testing cycle and opens them again before the next test cycle · COLLECTOR_SLOW_DATABASE_CONNECTION: If it is set to 0 or it is not present then the collector process only locks the common configuration file if it has already queried everything from the database. PVSR uses more memory this way but even a very slow database connection will not be resulted in data collection outages · COLLECTOR_CREATE_EQ (has category): the category is the ID of the appropriate passive measurement server or the default string. The value must the ID of one of the sites that belongs to this measurement site group. If this parameter is specified, then the available new pieces of equipment will be automatically created under the given site (for more details see the description of the ASCII server) · COLLECTOR_CREATE_MEASUREMENT (has category): the category is the ID of the appropriate passive measurement server or the default string. Its value must be 1. If the parameter is specified, then the available new measurements will be automatically created under the given equipment (regardless of this setting, the measurements are displayed for a new piece of equipment) (for more details see the description of the ASCII server) · COLLECTOR_DELETE_EQ (has category): the category is the ID of the appropriate passive measurement server or the default string. If the parameter is specified, then after that many days the equipment is automatically deleted if it has no new measurements (for more details see the description of the ASCII server) · COLLECTOR_DELETE_MEASUREMENT (has category): the category is the ID of the appropriate passive measurement server or the default string. In contrast to the previous parameters, the meaning of this parameter depends on whether the type of the measurement server is passive or active. If the value is not set, then its default value is 0, but it is important to note that during the install the default category is set with the value 1 o Passive: the value is given in days. If the parameter is specified and it is nonzero, then the measurement is automatically deleted if it has no new measurement value (for more details see the description of the ASCII serve) o Active discoverable: If it is set to zero, then the measurements are not deleted even if they are disappeared from the equipment configuration. Naturally, they can deleted with equipment modification through the user interface, until they possibly already appear · USE_INTERFACE_IP_ADDRESS (it has a category and may have a subparameter): the category is the ID of the appropriate measurement server group or default. If its value is 1, then interface measurements can be named based on their IP addresses. It can also have subparameters in which case those are interpreted as regular expressions and the IP addresses are only used if at least one of them matches the name of the equipment · SOAP_SERVER_LISTEN_PORT: the SOAP server listens on this port for requests · SOAP_MAX_CONCURRENT_SESSIONS: maximum number of available concurrent SOAP sessions. If not specified then there is no limit · TRAP_LIMIT: how many traps should be sent by the server component’s sub-process that executes one measurement cycle before waiting the number of seconds specified in the TRAP_WAIT parameter. Its default value is 30. · TRAP_WAIT: the threshold processing system’s sub-process that executes one measurement cycle should wait this many seconds after it already sent TRAP_LIMIT many traps. Its default value is 1 · CLEARED_TRAP_COUNT: this many positive traps should be sent by the thresholds processing system, if the threshold condition terminates the alarm and the continuous alarm is set for the threshold. Its default value is 1 · SNMP_TRAP_PORT: the event processing module receives the SNMP Traps on this port · SYSLOG_PORT: the event processing module receives the syslog messages on this port · CHART_SERVER_LISTEN_PORT: the number of the TCP port on which the Chart Server should listen. Recommended: 4444 · CHART_BG_COLOR: the background color of charts in hexadecimal RRGGBB format · CHART_VALUE_BG_COLOR1 and CHART_VALUE_BG_COLOR2: the background color of the value field of charts specified in hexadecimal RRGGBB format. If the second variable is also specified, then the system generates a color gradient between the two colors for the background, in which case the generated image is in PNG format instead of GIF, its size is slightly larger and the generation takes a little longer. Both colors are specified by default · CHART_MISSING_VALUE_COLOR: the background color of charts in hexadecimal RRGGBB format if a measurement data is missing · CHART_NO_VALUE_COLOR: the background color of charts in hexadecimal RRGGBB format if there is no measurement data · DEFAULT_CHART_FIRST_VALUE_COLOR: what should be the color of the first measurement values on the basic chart (by default green), the value should be specified in hexadecimal RRGGBB format, e.g. FF0000 · DEFAULT_CHART_SECOND_VALUE_COLOR: what should be the color of the second measurement values on the basic chart (by default blue), the value should be specified in hexadecimal RRGGBB format, e.g. FF0000 · DEFAULT_CHART_FIRST_VALUE_TYPE: what should be the type of the first measurement values on the basic chart. Possible values are: “A” for area, “B” for bar and “L” for line, the default value is “A” · DEFAULT_CHART_SECOND_VALUE_TYPE: what should be the type of the second measurement values on the basic chart. Possible values are: “A” for area, “B” for bar and “L” for line, the default value is “L” · DEFAULT_CHART_FIRST_VALUE_TRANSPARENT: whether the first measurement values on the basic chart should appear transparent. Possible values are 0 and 1, the default one is 0 · DEFAULT_CHART_SECOND_VALUE_TRANSPARENT: whether the second measurement values on the basic chart should appear transparent. Possible values are 0 and 1, the default one is 0 · FLASH_CHARTNUM_MAX: it governs the maximum number of JavaScript chart elements displayed at any time. Its value is 40 if not specified, but every user can override it on the Preferences pages. The actually used value is three times more than the one given here · FLASH_MAX_IMMEDIATE_REQUEST_FOR_ONE_PAGE: it governs the maximum number of JavaScript chart data request sent by the client to the server when someone opens an equipment in the Measurement menu. If according to this value the initial number of charts after opening the equipment would be less than according to the FLASH_CHARTNUM_MAX parameter, then this parameter will determine the initial number of JavaScript charts. If the value is not specified then it is set to 20. The actually used value is three times more than the one given here · RESTART_COLLECTOR_AFTER: restarts the collector processes after this many days (fractions can also be specified). Its recommended value is one week · RESTART_THRESHOLD_AFTER: restarts the threshold processes after this many days (fractions can also be specified) · RESTART_REPORT_AFTER: restarts the report processes after this many days (fractions can also be specified) · DASHBOARD_URL_FOR_MEASUREMENTS: if it is set, then a Dashboard submenu is also displayed in the Measurement menu item, which opens the required URL · DASHBOARD_URL_FOR_ALARM: if it is set, then a Dashboard submenu is also displayed in the Alarms menu item, which opens the required URL · WIMAX_FDD_MAX_SU_PER_BST: the maximum number of allowed SU data collection on a BST · DISABLE_LOW_TABLESPACE_SPACE_ERROR (has category): this can be used to disable the Oracle tablespace usage checks. The tablespace name must be used in uppercase for the category or the string __all__ for all tablespaces. The specified value must be 1 or 2 · DISABLE_LOW_DISK_SPACE_ERROR (has category and subparameter): this can be used to disable the disc capacity checks. The category is the exact server name as specified on the Settings => Servers => Server configuration page. The subparameter is the disc partition, its value must match the "Mounted on" value from the df command line utility, for example /, /var, /data, …: [pvsr@pvsr]$ df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda5 540945768 470121776 42902224 92% / /dev/sda3 19840924 1572240 17244544 9% /var /dev/sda1 497829 16359 455768 4% /boot tmpfs 3053424 0 3053424 0% /dev/shm /dev/sdb1 288252476 270796084 2813952 99% /data · USE_CISCO_DESCRIPTION: if it is set to 1 then PVSR uses the Cisco interface description texts to name the interface measurements. If it is not set then the Cisco interface description texts are only used as additional interface parameters · CUSTOM_PASSWORD_PAGE: if the used authentication method does not support the password changing (for example LDAP or RADIUS) then by default PVSR does not display the password changing menu item. However if this parameter is set then it displays the menu item, and if the user clicks on it then the URL specified in the parameter is opened · USE_OLD_EQUIP_ALARM_PAGE: if its value is 1 then PVSR shows the charts for the alarming measurements in the Alarms menu when viewing an equipment, instead of a threshold list · DO_NOT_GROUP_ALARMS: if its value is 1 then PVSR do not group together thresholds on the Alarms pages based on their names and the measurements in their definition · SHOW_VALUES_FOR_INACTIVE_ALARMS: if its value is 1 then PVSR also shows the values of measurements in non-violating thresholds on the Alarms pages in real-time mode, not just the values of measurements in violating thresholds · REPORT_LAST_WHEN_DATES: if its value is 1 then PVSR shows in the reports the last time the minimum or maximum was seen, instead of showing the first time the minimum or maximum was seen · CISCO_MDT_UDP_PORT: if set then the Telemetry data collector module will start listening on this UDP port for incoming Cisco MDT telemetry packets · CISCO_MDT_TCP_PORT: if set then the Telemetry data collector module will start listening on this TCP port for incoming Cisco MDT telemetry packets · CISCO_MDT_GRPC_WITHOUT_SSL: if set then the Telemetry data collector module will start listening on this HTTP2 port for incoming Cisco MDT telemetry packets in GRPC format, without SSL encryption · CISCO_MDT_GRPC_WITHOUT_SSL: if set then the Telemetry data collector module will start listening on this HTTP2 port for incoming Cisco MDT telemetry packets in GRPC format, with SSL encryption. · CISCO_MDT_GRPC_CERT_FILE, CISCO_MDT_GRPC_KEY_FILE and CISCO_MDT_GRPC_CERT_PASSWORD: these parameters serve two purposes: they are used if PVSR is listening for GRPC calls using SSL or when PVSR is using gNMI with SSL. The certificate and the key file parameters must be set and the password might be set, similarly to the QUICK_EVAL_THRESHOLD_SSL_... parameters |