XECfgParm.dat File Parameters

Transcription

1 APPENDIX B This chapter describes parameters found in the dat file XECfgParm.dat. However, this information is not provided so that users can edit the file. Rather, the parameter descriptions are provided in this chapter to enable users to better understand what these parameters are and how they are used because these parameters are used by every process of the Cisco MGC network element. XECfgParm.dat parameters take the following syntax: facilityname.parametername = parametervalue Valid facility names are: almm Alarm Manager amdmpr Alarm / Measurement Dumper cdrdmpr CDR Dumper cfgm Configuration Manager engine Call processing engine foverd Failover Daemon iochanctl Controls all channel controllers iochanmgr I/O Channel Managers logger Log Server measm Measurement Manager mmdb TimesTen Main Memory Data Base Process MML MML mmsagt Measurement Manager SNMP Agent OPERSAGT Operational SNMP Agent pom Provisioning Object Manager procm Process Manager PROVSAGT Provisioning SNMP Agent replicator Replicator If no match is found for a facility-specific parameter, the file is searched for a match on the default facility. B-1

2 for Release 7.4 Appendix B for Release 7.4 The XECfgParm.dat file configuration parameters for Release 7.4 are presented alphabetically in. This list of parameters is provided as a reference. Do not edit any parameters that are not listed in this appendix unless instructed by Cisco technical support, or your system might not work as intended. The values for these parameters are case sensitive and must be entered exactly as displayed in the following table. XECfgParm.dat File s *.autonomous Enables a process, for example the engine, to be started without the system. Default: false B-2

3 Appendix B for Release 7.4 XECfgParm.dat File s (continued) *.ClearingLocation Specifies whether the Clearing Location field in Call Context is overridden before outputting LRelease from LCM. The reason this may be needed is as follows:-ni2+ from the NAS always sends a clearing location of USER, which is generally mapped to clearing location of USER, but the switch receiving the release message may want to receive a location of TRANSIT so that the call can be re-routed. This clearing location property provides this ability. 0 = Normal mapping behavior, LCM will not override the Clearing Location field in Call Context. 1 = LCM will override the Clearing Location in Call Context with LOCATION_USER 2 = LCM will override the Clearing Location in Call Context with LOCATION_ PRIVATE_LOCAL 3 = LCM will override the Clearing Location in Call Context with LOCATION_ PUBLIC_LOCAL 4 = LCM will override the Clearing Location in Call Context with LOCATION_TRANSIT 5 = LCM will override the Clearing Location in Call Context with LOCATION_ PUBLIC_REMOTE 6 = LCM will override the Clearing Location in Call Context with LOCATION_ PRIVATE_REMOTE 7 = LCM will override the Clearing Location in Call Context with LOCATION_ INTERNATIONAL 8 = LCM will override the Clearing Location in Call Context with LOCATION_ INTERWORKING 9 = LCM will override the Clearing Location in Call Context with LOCATION_ LOCAL_INTERFACE 10 = LCM will override the Clearing Location in Call Context with LOCATION_ LOCAL_LOCAL 11 = LCM will override the Clearing Location in Call Context with LOCATION_ LOCAL_REMOTE 12 = LCM will override the Clearing Location in Call Context with LOCATION_ PACKET_MANAGER 13 = LCM will override the Clearing Location in Call Context with LOCATION_ UNKNOWN Default: 0 (Normal mapping behavior) Option 13 may not be valid for all solutions. B-3

4 for Release 7.4 Appendix B XECfgParm.dat File s (continued) *.chkptport Port number used between peer components or processes for check-pointing. Value: Any unused port number. Default: 2001 Leave this value as the default. If you have two Cisco MGC hosts in a failover configuration, both fields in the XECfgParm.dat files should contain the same value. *.CPUTimerInterval *.datadir Specify the interval, in milliseconds, at which the CPU utilization level of the Cisco MGC is sampled. Recommended Value: milliseconds. Default: Location of the data directory. Default:../var *.datasourcename Used by the MMDB to obtain the data source name for the ODBC connection. Default: howdydb *.debuglevel Determines level of debugging detail if debugging is initiated. Default: high B-4

5 Appendix B for Release 7.4 XECfgParm.dat File s (continued) *.DefaultLocation Specifies whether to override the default location field in call context. This is so that the user can define a customer-specific default location for the system, which may differ from the default location set in the type definition of the protocol. The default location property provides this ability. 0 = Normal protocol-defined default value; LCM will not override the default location field in call context. 1 = LCM will override the default location in call context with LOCATION_USER 2 = LCM will override the default location in call context with LOCATION_ PRIVATE_LOCAL 3 = LCM will override the default location in call context with LOCATION_ PUBLIC_LOCAL 4 = LCM will override the default location in call context with LOCATION_TRANSIT 5 = LCM will override the default location in call context with LOCATION_ PUBLIC_REMOTE 6 = LCM will override the default location in call context with LOCATION_ PRIVATE_REMOTE 7 = LCM will override the default location in call context with LOCATION_ INTERNATIONAL 8 = LCM will override the default location in call context with LOCATION_ INTERWORKING 9 = LCM will override the default location in call context with LOCATION_ LOCAL_INTERFACE 10 = LCM will override the default location in call context with LOCATION_ LOCAL_LOCAL 11 = LCM will override the default location in call context with LOCATION_ LOCAL_REMOTE 12 = LCM will override the default location in call context with LOCATION_ PACKET_MANAGER 13 = LCM will override the default location in call context with LOCATION_ UNKNOWN Default: 0 (Normal protocol-defined default value) Option 13 may not be valid for all solutions. B-5

6 for Release 7.4 Appendix B XECfgParm.dat File s (continued) *.desiredplatformstate Determines the desired platform state. master, if you have two (active and standby) Cisco MGC hosts slave, if you have two (active and standby) Cisco MGC hosts standalone, if you have a single-host system Default: none The value used is site specific. For example, use the values master and slave if you have two (active and standby) Cisco MGC hosts. Enter standalone if you have a single-host system. *.disablemeas Disables the collection of measurement data. true = disables data collection false = data is collected Default: false *.eventtrace engine.sysgsmtimerinterval *.FastConnect Used by developers only to trace events at the application level. Allows group service messages (GSMs used to advertise the state of circuits) to be sent at a periodic rate from the SS7 side of the network to the IP side of the network. Valid values: 1000 to Default: Allows LCM messages to pass through. 0 = Passes all signals to LCM 1 = Disables signal to LCM for "CallProceeding" received from NAS 2 = Disables signal to LCM for "CallProceeding" or "Progress" received from NAS 3 = Disables signal to LCM for "CallProceeding", "Progress", or "Alerting" received from NAS. B-6

7 Appendix B for Release 7.4 XECfgParm.dat File s (continued) *.GWClearChannelAlgorithm *.homedirroot Allows the use of the clear channel 64K unrestricted data transfer between gateways. null = do not use clear channel algorithm clear channel = use clear channel algorithm Default: null Location of the home directory. Default: /opt/ciscomgc iochanctl.ituisnewzealand At startup, the IOCM reads the iochanctl.ituisnewzealand boolean flag in XECfgParm.dat to see if the ITU implementation of MTP3 is to be set with NewZealand specific parameters. If the flag is set to true, then the associated MTP3 parameters are set to meet the following requirements: The MTP3 restart procedure must be disabled. The SS7 IOCC currently provides this capability by setting timers T20 and T21 to zero. The priority of all MTP3 messages must be set to zero. The RCT (Route Congestion Test) Procedure must be disabled. Set this parameter to true if running in or connecting to the Telecom New Zealand network. *.IP_Addr1 *.IP_Addr2 *.IP_Addr3 *.IP_Addr4 *.ipaddrlocala IP address of interface 1; used for signaling. IP address of interface 2; used for signaling. IP address of interface 3 (if installed); used for signaling. IP address of interface 4 (if installed); used for signaling. First local IP address; used for checkpointing and failover heartbeats if you have active/standby Cisco MGC hosts. This is typically the same value as *.IP_Addr1. B-7

8 for Release 7.4 Appendix B XECfgParm.dat File s (continued) *.ipaddrlocalb Second local IP address; used for checkpointing and failover heartbeats if you have active/standby Cisco MGC hosts. If your configuration does not use an external card, leave this setting as the default value, 0.0. *.ipaddrpeera First corresponding peer IP address; used for checkpointing and failover heartbeats. If you have two Cisco MGC hosts in a failover configuration, this value is the IP address of the second host. *.ipaddrpeerb Second corresponding peer IP address; used for checkpointing and failover heartbeats. If your configuration does not use an external card, leave this setting as the default value, 0.0. *.logdirectory Location of the active and rotated log files. Default:../var/log Make sure the log file has write permission for the LogServer. *.logfilenameprefix Combined with the.log extension, defines the filename for log files. Default: platform Example: engine This setting can also redirect process messages from the default log file to a specified log file. For example, engine.logfilenameprefix = engine instructs the log server to redirect messages from the engine process to the dedicated engine.log file. This functions with or without *.logdirectory. B-8

9 Appendix B for Release 7.4 XECfgParm.dat File s (continued) *.logmsgdrop Controls whether the log server drops debug-level messages when the UNIX domain socket used for log server communication is full. true = debug messages are dropped false = debug messages are not dropped Default: true If you set this parameter to false for the engine and the engine logging level is Debug, the system can fail at high call rates. B-9

10 for Release 7.4 Appendix B XECfgParm.dat File s (continued) *.logprio Defines the initial default logging level used by logging clients when sending messages to the logging server. Use the chg-log MML command to change logging levels after installation. You can specify different logging levels for each process. For example, engine.logprio = Info This setting is the only way to modify the logging level of the current MML process. The chg-log command does not affect current MML process logging levels. The values for this parameter are case sensitive, and the first letter must be capitalized. Debug This priority is used only for detailed debugging messages. Logging at this priority is not recommended during production because this causes a large volume of messages to be logged, which degrades system performance and can cause failover problems. Trace These messages capture protocol traffic. This priority is used for debugging. Info These messages indicate an operation that is proceeding as expected. Warning These messages indicate a problem exists that does not prevent the system from operating. This is the normal, default logging level for production. Error These messages indicate an unexpected error that is recoverable but degrades performance. Critical These messages indicate errors so severe that a process cannot continue operating. Default: Error Do not change this value unless you are debugging. B-10

11 Appendix B for Release 7.4 XECfgParm.dat File s (continued) *.LongCallTime Monitors call length and sets the system to trigger an alarm when a call length reaches a certain level. Default: milliseconds (6 hours) Typically, leave this value as the default. You can change it, if necessary, based on billing requirements. *.MDLANumberScreening *.MgcpBehavior Specifies which number to use as the A Number screening value. 0 = use Calling Party Number 1= use Redirecting Number Default: 0 Regulates VSC engine behavior to allow different MGCP gateway types to return different codes for the same error. Value range: Integer 0 No action 1 Prevents the VSC from reusing a circuit after a CRCX failure (return code 501); VISM and MX Prevents the VSC from reusing a circuit after a CRCX failure (return code 502); 5300 Default: 0 Additional differences can be handled by adding enumerated values. *.numberofthreads Specifies the number of threads generated by multi-threaded processes such as the engine, the log master, and so on. Corresponds to the number of CPUs in your configuration. 0 = single CPU 1 = two CPUs 2 = four CPUs Default: 0 If you have a multi-cpu system (1 or 2), you must set engine.sysgeneratedcode to true. B-11

12 for Release 7.4 Appendix B XECfgParm.dat File s (continued) *.Ovl1AbateThresh Controls engine overload levels. This setting depends on the specified percentage of CPU utilization. If the Ovl1OnsetThreshold is reached, raising an alarm, the Ovl1RejectPercent action abates until this threshold value is reached, clearing the alarm. Value: 0 to 100 percent Default: 75 This value must be less than Ovl1OnsetThresh. *.Ovl1OnsetThresh *.Ovl1RejectPercent *.Ovl2AbateThresh Controls engine overload levels. This setting depends on the specified percentage of CPU utilization. If this threshold value is met, an alarm is raised and calls are rejected at the percentage defined by Ovl1RejectPercent. Value: 0 to 100 percent Default: 82 Controls engine overload levels. This setting depends on the specified percentage of CPU utilization. A percentage of new calls is rejected at this level. For example, 20% means that 1 out of 5 new calls are rejected at this level. Value: 0 to 100 percent Default: 25 percent Controls engine overload levels. This setting depends on the specified percentage of CPU utilization. If the Ovl2OnsetThreshold is reached, raising an alarm, the Ovl2RejectPercent action abates until this threshold value is reached, clearing the alarm. Value: 0 to 100 percent Default: 77 This value must be less than Ovl2OnsetThresh *.Ovl2OnsetThresh Controls engine overload levels. This setting depends on the specified percentage of CPU utilization. If this threshold value is met, an alarm is raised and calls are rejected at the percentage defined by Ovl2RejectPercent. Value: 0 to 100 percent Default: 90 B-12

13 Appendix B for Release 7.4 XECfgParm.dat File s (continued) *.Ovl2RejectPercent *.Ovl3AbateThresh Controls engine overload levels. This setting depends on the specified percentage of CPU utilization. A percentage of new calls is rejected at this level. For example, 20% means that 1 out of 5 new calls are rejected at this level. Value: 0 to 100 percent Default: 50 percent Controls engine overload levels. This setting depends on the specified percentage of CPU utilization. If the Ovl3OnsetThreshold is reached, raising an alarm, the Ovl3RejectPercent action abates until this threshold value is reached, clearing the alarm. Value: 0 to 100 percent Default: 85 This value must be less than Ovl3OnsetThresh. *.Ovl3OnsetThresh *.Ovl3RejectPercent *.OwnClli Controls engine overload levels. This setting depends on the percentage of CPU utilization. If this threshold value is met, an alarm is raised and calls are rejected at the percentage defined by Ovl3RejectPercent. Value: 0 to 100 percent Default: 93 Controls engine overload levels. This setting depends on the specified percentage of CPU utilization. A percentage of new calls is rejected at this level. For example, 20% means that 1 out of 5 new calls are rejected at this level. Value: 0 to 100 percent Default: 100 percent Common language location identifier; used for circuit query validation when circuit queries are supported. Value: Alphanumeric string, up to 11 characters. Default: TTTT-SS-BB-XXX Example: B-13

14 for Release 7.4 Appendix B XECfgParm.dat File s (continued) *.owntranspathid Identifies the local Cisco MGC host in a redundant configuration (same value as *.transpathid). The IDs must be unique in an active and standby pair. Value: Any integer up to 2 digits. Default (for the active Cisco MGC host): 01 If you have two Cisco MGC hosts in a failover configuration, enter this value in the *.peertranspathid field in the XECfgParm.dat file on the second host server. *.peertranspathid Identifies the peer Cisco MGC host in a redundant configuration. The IDs must be unique in an active and standby pair. Value: Any integer up to 2 digits. Default (for the standby Cisco MGC host): 02 If you have two Cisco MGC hosts in a failover configuration, enter the *.owntranspathid value from the XECfgParm.dat file of the second host server in this field. If you have a standalone configuration, leave it blank. *.platformid Enables the signaling controller to run more than one instance of the Cisco MGC software concurrently. Default: 1 B-14

15 Appendix B for Release 7.4 XECfgParm.dat File s (continued) processes.dat Warning Do not modify the processes.dat file. This file should remain unmodified, as delivered with the Cisco MGC software. If this file is modified, procm may core dump when you start the MGC software. Contains information about all processes on the system that the Cisco MGC is responsible for monitoring. There are three different monitoring levels: Active Process identified in the record that is controlled and monitored directly by the Process Manager. Passive Process identified in the record that does not communicate with the Process Manager. Monitoring Process periodically runs an executable or script and sets or clears an alarm based on the return code. This type of process may monitor other processes or tasks that can be checked programmatically, such as the amount of disk space, system daemon existence, and established process dependency. Additionally, this file contains information related to the frequency that the health of each process is checked and how to restart it. B-15

16 for Release 7.4 Appendix B XECfgParm.dat File s (continued) *.RedirectingATree Used to control A-number screening/analysis via A-digit tree. This parameter allows the analysis system to use the A-Digit tree for mapping to the BLACKLIST function on the Redirecting CLI value. It uses the A-Digit tree to allow for black screening on the redirecting number parameter included in the IAM. Currently, when the parameter MDLANumberScreening is set to 1 in the XECfgParm.dat file, screening is done on the redirecting number. This works when screening individual numbers but does not allow block ranges to be screened, as is the case when using DialPlan Screening in the Digit Tree functions. Use an editor such as vi to manually add the *.RedirectingATree parameter to the XECfgParm.dat file in the following file locations and set its value: /opt/ciscomgc/etc/xecfgparm.dat /opt/ciscomgc/etc/config_lib/new/xecfgparm.dat Valid values: 0 = Default; indicates the Calling Party Number (CGPN) that will be used for A-number screening/analysis via A-digit tree. 1 = Indicates that the Redirecting Number should be used for A-number screening/analysis via A-digit tree if the incoming signaling message contains both the CPN and Redirecting Number or just the Redirecting Number. This property is only effective when BLACKLIST is provisioned. If Screening is data filled and this property is set to 1, then Redirecting Number is used for screening. However, if result types other than BLACKLIST/SCREENING are encountered when Redirecting Number is used during A-number Tree Analysis, an alarm RedirectingNbrFail (informational alarm) is generated. B-16

17 Appendix B for Release 7.4 XECfgParm.dat File s (continued) *.runasdaemon Enables processes to run in the background. Default: False logger.runasdaemon = false procm.runasdaemon = true (runs in the background) MML.runAsDaemon = false Do not change the default values for these settings or the system might not operate correctly. For Release 7.4(7) and later, logger.runasdaemon should be false. For earlier releases, this should be true. *.SelectTermCustGrpId *.sm_meas_baseaddr This boolean parameter applies only to Nailed Solutions. If this parameter is not defined, it defaults to False. If SelectTermCustGrpId is set to True and CUSTGRPID of the Originating Leg SigPath is 0000, then you must select CUSTGRPID of the Terminating Leg SigPath. If SelectTermCustGrpId is set to False, you should always select CUSTGRPID of the Originating Leg SigPath. Default: False Indicates the memory size of the base address. Default: 2048 *.stport Port number used between peer components or processes. Enter any unused port number, for example, If your configuration uses a Cisco SLT, enter the port number on the Cisco SLT. If you have two Cisco MGC hosts in a failover configuration, enter a different number for this value in the XECfgParm.dat file on the secondary host, for example, B-17

18 for Release 7.4 Appendix B XECfgParm.dat File s (continued) *.SyscheckpointEnabled Enables or disables checkpointing. false = Disables checkpointing. Calls are not preserved during a switchover, and status messages are not sent to the replicator. true = Enables checkpointing. Calls that are in the talking state are preserved and survive a control switchover. All status checkpointing information is sent to the replicator on the active side. Default: false If you have two Cisco MGC hosts in a failover configuration, enter true. If you have a standalone configuration, enter false. *.tablesfile Location of the database directories. Default:../etc/tables.dat *.tempdir Location of the temporary files. Default: /tmp *.transpathid Identifies the local Cisco MGC host in a redundant configuration. The IDs must be unique in an active and standby pair. Value: Any integer up to 2 digits. Default (for the active host): 01 If you have two Cisco MGC hosts in a failover configuration, this number must be different in the XECfgParm.dat file for each host. B-18

19 Appendix B for Release 7.4 XECfgParm.dat File s (continued) *.VSCNetworkPlacement Determines Cisco MGC placement (AT or IXC) and bias routing accordingly. Nanp_AT Nanp_IXC NULL 0 Default: NULL If you do not set this property, all calls will route according to called number or some other criteria, not Carrier ID. cfgm.recovdbfile Storage location of the configuration manager recovery information. Default:../var/cfgMRecovery diskmonitor.limit Number of days to preserve before disk trimming is initiated. Default: 7 diskmonitor.optfilesys diskmonitor.softlimit List of optional file systems to monitor. Default: (blank) Works with diskmonitor.threshold to prevent the disk from filling up and stopping the Cisco MGC. If true, an override of the preserve limit is allowed. true false Default: false B-19

20 for Release 7.4 Appendix B XECfgParm.dat File s (continued) diskmonitor.threshold diskmonitor.cdrrmfinished cdrdmpr.calldetail Erases old log files to free disk space. The threshold is the percent the disk is full before trimming starts. Value: Any integer from 1 to 100 (% of threshold). Default: 80 Controls removal of CDRs that have been processed. This parameter controls whether files should be deleted immediately (the default) or kept for X days. This parameter is valid only when a BAM system is pulling CDR files and renaming them.finished upon successful transfer. Value: 0 (default - delete immediately), or non-zero integer indicated days to delay before being deleted Default: 0 Specifies that call detail record (CDR) files may be automatically converted from binary format to ASCII, comma-delimited format. Default: /opt/ciscomgc/local/cdbscript.sh Optional: /opt/ciscomgc/bin/converter (if binary CDR files need to be converted to ASCII) For maximum performance, change this value to none, as follows: cdrdmpr.calldetail = # The default CDR file format has changed from an ASCII format in Release 4 to a binary format in Release 7. The ASCII file has a.csv extension. For more information on generating and viewing CDR files, see the Cisco Media Gateway Controller Software Release 7 Operations, Maintenance, and Troubleshooting Guide. B-20

21 Appendix B for Release 7.4 XECfgParm.dat File s (continued) dmpr.opencdr Specifies whether the standard data dumper should write out CDR files. true = Standard data dumper opens a CDR file and log the call data blocks (CDB). false = Standard data dumper does not open a CDR file and does not log CDBs. Default: true The default format for CDR files has been changed since release 4 from an ASCII format to a binary format. Use the dmpr.calldetail parameter to convert the files to an ASCII format, if necessary. engine.auditoverloadlvl Specifies a queue level where audit processing is deferred to reduce the load on the system. When the queue capacity is at this level or higher, auditing is not canceled, but it is deferred until the queue capacity returns to below this level. 0 to 100 percent 0 = auditing is disabled, regardless of the system load. 100 = auditing is enabled, regardless of the system load. Default: 25 percent This is a platform-specific value and depends on your system installation. No auditing is available for nailed trunks. engine.audittimerinterval Time interval in milliseconds between two batches of audits. Value: Any positive integer. Default: 500 This is a platform-specific value and depends on your system installation. No auditing is available for nailed trunks. engine.call_mem_block_size Block of memory allocated per call; used by MDL. Value: Integer Default: B-21

22 for Release 7.4 Appendix B XECfgParm.dat File s (continued) engine.call_mem_chunk_size engine.cdrencodingformat engine.cdrmessagetypes engine.cdrtimestamp engine.cmmdlfile Memory chunks allocated from the block of memory designated with engine.call_mem_block_size. Value: Integer Default: Specifies the call detail record (CDR) file encoding format. AnsiCDB = North American ItuCDB = European CustCDB = Custom Default: AnsiCDB Specifies which call detail blocks (CDBs) are recorded during a call. Default: 1010, 1020, 1030, 1040, 1050, 1060, 1070 Example: 1060, 1110 Each number represents a point in a call is required is an external value, used for TCAP. If you choose 1110, you must specify milliseconds for the CDRtimeStamp parameter. Refer to the the chapter Detailed CDB Description in the Cisco Media Gateway Controller Software Release 7 Billing Interface Guide for information on CDE tags contained in each CDB. Specifies the time stamp unit in seconds or milliseconds. If a BAM is being used for billing and measurements, the value must be M. S = seconds (Default) M = milliseconds Location of call processing libraries. Default:../lib/cc engine.lcmmdlfile Location of call processing libraries. Default:../lib/lcm B-22

23 Appendix B for Release 7.4 XECfgParm.dat File s (continued) engine.maxauditcics Number of circuit identification codes (CICs) that can be audited at a specified interval. 24 = North America (T1) 32 = Europe (E1) Default: 32 engine.mdodir Location of call processing libraries. Default:../lib/ engine.syscdrcollection Designates the format of call detail records (CDRs). true = Invalid for Release 7.4 and above. false = generates binary format CDRs (default) Default: false Setting this to a value of true for Release 7.4 and above is not valid and may have deleterious effects on the system. engine.sysclival Enables or disables Calling Line Identity (CLI) validation processing on calls. true = enables CLI validation false = disables CLI validation Default: false B-23

24 for Release 7.4 Appendix B XECfgParm.dat File s (continued) engine.sysgeneratedcode Determines whether compiled or interpreted code is used. true = system uses compiled code false = system uses interpreted code Default: true Compiled code runs faster than interpreted code. Typically, this value should be true. If your configuration uses multiple CPUs, this value must be true. engine.sysgrsblocksize engine.sysgrstimerinterval engine.sysgsmtimerinterval engine.sysmaxoverlap Specifies the number of simultaneous Circuit Group Reset (GRS) messages to send in each block, based on the timing interval set in the engine.sysgrstimerinterval parameter. This parameter operates independently for each SS7 route (each OPC/DPC pair). Value: Any integer Default: 0 Example: 1 Specifies the interval, in milliseconds, between blocks of GRS parameters when the engine.sysgrsblocksize parameter is used. The timer interval runs from the start of sending the first GRS message in each block to the first message in the next block. Value: Any integer. Default: 0 Example: 1000 Allows group service messages (GSMs used to advertise the state of circuits) to be sent at a periodic rate from the SS7 side of the network to the IP side of the network. Valid values: 1000 to Default: Maximum number of digits required before a call is considered complete; used in overlap signaling. Default: 28 B-24

25 Appendix B for Release 7.4 XECfgParm.dat File s (continued) engine.sysmdlmemoryreduction Controls use of MDL memory reductions. 0 = MDL memory reductions not used (maximum performance) 1 = MDL memory reduction improvements used Default: 0 For performance-critical configurations, use the default value. For memory-critical configurations, set this value to 1. engine.sysminoverlap Minimum number of digits required before a call is considered valid; used in overlap signaling. Default: 0 engine.syspropagatechanavail In a classic signaling controller configuration, propagates service messages between channels in the event of a channel failure. true = messages propagated false = messages not propagated (default) engine.sysscreeningcheck Enables or disables the call screening database. If you do not have the database environment set with all of the required data populated, set this value to false. Set this value to true if you have the database and want the system to access it. true = enabled false = disabled Default: false Setting this parameter to true will impact system performance because it will reduce MAX CPS and the maximum number of sustained calls. B-25

26 for Release 7.4 Appendix B XECfgParm.dat File s (continued) engine.syssgcpretrycount Maximum number of simple gateway control protocol (SGCP) retry messages after a failure. Default: 3 engine.syssgcpretrytimerinterval The interval between SGCP message transmissions, in milliseconds. Default: 1000 engine.systracelevel A debugging tool that allows for different levels of engine tracing. Default: 3 engine.sysvirtualswitch engine.versiontimeoutvalue foverd.abswitchport Indicates whether the Cisco MGC host functions as a signaling controller or a virtual switch controller. 0 = signaling controller (nailed trunks, no auditing is initiated) 1 = virtual switch controller (switched trunks) Default: 0 Defines the timeout interval in number of milliseconds for version messages sent to the MGW. This delay determines how long the Cisco MGC will wait for response from the MGW during the exchange of features prior to the audit. Value: Any integer. Default: Port used for communication with the A/B switch. Value: /dev/term/x Example: /dev/term/b If your configuration does not use an A/B switch, use the default value (/dev/null). B-26

27 Appendix B for Release 7.4 XECfgParm.dat File s (continued) foverd.abswitchtestinterval Time interval in milliseconds between attempts to verify that an A/B switch is present. Default: This parameter only applies if your configuration uses an A/B switch. foverd.acktimeout Maximum time, in milliseconds, that the failover daemon will wait for an ACK or NOACK message to be received from the peer failover daemon. For each message the failover daemon sends, the peer failover daemon sends an ACK or NOACK message to indicate that the peer is still functioning. Default: 1000 milliseconds (1 second). You can change the default value to a value more appropriate for your system installation. foverd.commretryinterval Time interval in milliseconds between attempts to open a connection. Connection types include: Connection to the peer failover daemon Connection to the A/B switch Connection to the ARU Default: milliseconds (30 seconds). You can change the default value to a value more suited to your system installation. foverd.conn1type Sets the connection type for connection number 1. serial socket Typically, set this value to socket. B-27

28 for Release 7.4 Appendix B XECfgParm.dat File s (continued) foverd.conn2type Sets the connection type for connection number 2. serial socket Typically, set this value to socket. foverd.conn3addr Specifies the address of the peer system. Example: /dev/term/b If your configuration does not use connection number 3, enter /dev/null (default). If your configuration uses an 8-port connector as a serial connection for failover, you must modify the read-write permissions for the connection. For more information, see the Release s for the Cisco Media Gateway Controller Software Release 7. foverd.conn3type Sets the connection type for connection number 3. serial socket Typically, set this value to serial. foverd.delaytimeout foverd.forceshuttimeout foverd.graceshuttimeout foverd.heartbeatinterval Maximum time in milliseconds that the failover daemon can delay at startup before sending messages to its peer. This is also the delay offset that is added when the two failover daemons become too closely synchronized. Default: 1000 milliseconds (1 second) Maximum time in milliseconds that the failover daemon waits before forcefully shutting down the platform. Default: 1000 milliseconds (1 second) Maximum time in milliseconds that the failover daemon waits before gracefully shutting down the process manager, which shuts down the processes it controls. Default: 6000 milliseconds (6 seconds) Maximum time in milliseconds between heartbeat messages from the peer failover daemon. This interval defines the frequency that the failover daemon exchanges heartbeat messages with its peer. Default: 4000 milliseconds (4 seconds). B-28

29 Appendix B for Release 7.4 XECfgParm.dat File s (continued) foverd.iplocalporta Port number used for IP communication. Default: 0 If you have two Cisco MGC hosts in a failover configuration, enter this value for the foverd.ippeerporta field in the XECfgParm.dat file on the secondary host. foverd.iplocalportb Port number used for IP communication. Default: 0 If you have two Cisco MGC hosts in a failover configuration, enter this value for the foverd.ippeerportb field in the XECfgParm.dat file on the secondary host. foverd.ippeerporta Port number used for IP communication. Default: 0 If you have two Cisco MGC hosts in a failover configuration, enter this value for the foverd.iplocalporta field in the XECfgParm.dat file on the secondary host. foverd.ippeerportb Port number used for IP communication. Default: 0 If you have two Cisco MGC hosts in a failover configuration, enter this value for the foverd.iplocalportb field in the XECfgParm.dat file on the secondary host. foverd.peercommtimeout Maximum time in milliseconds without communication with the remote system. At the expiration of this period, the remote system is assumed to be unavailable and failover is triggered automatically. Default: milliseconds (10 seconds) A timeout value that is too small can cause a false failover, resulting in possible service interruptions. B-29

30 for Release 7.4 Appendix B XECfgParm.dat File s (continued) foverd.statusrptinterval foverd.transitiontimeout iochanctl.dpnsstestframes Time interval in milliseconds that governs the frequency with which the failover daemon logs statistics on the different connections and any failures it encountered exchanging messages with its peer. Logs are created in the log directory. Default: milliseconds (10 minutes) Maximum time in milliseconds allowed for transitions between different states of the failover daemon. This timeout determines how long the system waits for a graceful transition to a new state before forcing the transition. If a timeout occurs, the system is restarted. Default: milliseconds (10 seconds). Enables DPNSS to generate test frames. true = if DPNSS is running, test frames are generated false = test frames are not generated Default: true iochanmgr.alarmtimer This parameter is obsolete and should be set to 0. iochanmgr.evttimer Frequency, in milliseconds, at which the queue is scanned for messages. Default: 100 iochanmgr.hbtimer iochanmgr.resumeacktimer iochanmgr.sendthreshold This parameter is reserved for future use. Amount of time VSC waits to get a MGMT_RESUME_ACK_RSP message from a gateway, after sending a MGMT_RESUME_REQ message fro a BSM session set. Values are 1 to 2 seconds. Default: 1 Maximum number of events sent from the queue at one time. Default: 10 B-30

31 Appendix B for Release 7.4 XECfgParm.dat File s (continued) iochanmgr.sessionpausetimer iochanmgr.statdiscardthreshold Amount of time VSC waits for a BSM session set to recover from failure before declaring the session set failure. Values are 1 to 10 sec. Default: 8 Size of the control queue that triggers discarding of all queued stat events. Default: 40 iochanmgr.stattimer Frequency, in milliseconds, at which measurements are collected in the Transpath input/output system (TIOS). Default: milliseconds iochanmgr.trace Creates unit test tracing of line and channel state machines. Generates a considerable amount of information to the log. Set to a value only when you are debugging a particular problem with line or channel service state problems. 0 x 0 = default 0 x 1 = trace logger.daemonaddr Specifies the name of the local socket used by the log server daemon. The daemon listens for connections on this address, and client programs attempt to connect to the daemon at this address. Default:../var/log/lsd_addr If this setting is missing from the XECfgParm.dat file, the log server daemon does not run. B-31

32 for Release 7.4 Appendix B XECfgParm.dat File s (continued) logger.filerotateinterval Triggers a file rotation based on the time elapsed since the previous rotation. Default: 1440 minutes (24 hours) This timer is reset after any rotation occurs, regardless of the cause or trigger of the rotation. logger.filerotatesize Triggers a file rotation based on the size of the active file. A file rotation triggered by this parameter also resets the logger.filerotateinterval timer. Default: 100MB The file size may grow somewhat larger than this parameter indicates due to the verbosity of the logging levels currently in effect. logger.numthreads MML.chg-cfg Determines whether the PXE logger should run in a separate thread from the rest of the application. A value of 0 runs the logger synchronously with the application; a value of 1 runs the logger in a separate thread. Value: 0/1 (Values less than 0 get reset to 0; values greater than 1 get reset to 1.) Default: 0 Timeout value for the chg-cfg MML command in milliseconds; overrides MML.timeout. Default: milliseconds This MML command is obsolete. MML.set-sc-state Timeout value for the set-sc-state MML command in milliseconds; overrides MML.timeout. Default: 8500 milliseconds MML.snd Timeout value for the snd MML command in milliseconds; overrides MML.timeout. Default: milliseconds B-32

33 Appendix B for Release 7.4 XECfgParm.dat File s (continued) MML.startPM Timeout value for the startpm MML command in milliseconds; overrides MML.timeout. Default: /etc/init.d/ciscomgc start MML.stopPM Timeout value for the stoppm MML command in milliseconds; overrides MML.timeout. Default: /etc/init.d/ciscomgc stop MML.timeout Timeout for MML commands, in milliseconds. Default: milliseconds MML.vld-cic Timeout value for the vld-cic MML command in milliseconds; overrides MML.timeout. Default: milliseconds pom.datasync Indicates that the Provisioning Object Manager (POM) should synchronize the provisioning data at startup. true = POM is enabled, data is synchronized false = POM is disabled, no data synchronization (default) If you have two Cisco MGC hosts in a failover configuration, set this value to true. If you have a standalone Cisco MGC, set this value to false. B-33

34 for Release 7.4 Appendix B XECfgParm.dat File s (continued) pom.port In a failover configuration, indicates the port number the POM uses to communicate with its peer. Value: Any integer from 4001 to 4050 Default: 4001 or default This is a platform-specific value and depends on your system installation. You should only modify this value if the default port (4001) is being used by another process or application. procm.almdwellinterval Seconds that the process manager must wait before clearing an alarm. Default: 15 seconds procm.logdbfile procm.mincheckhealthinterval Specifies the location of the log level storage. Default:../var/procMLogTable Seconds at which a process can generate heartbeats. Default: 10 seconds procm.mincheckhealthtimeout Seconds at which a timeout can occur. Default: 2 seconds procm.minkillgraceperiod Seconds that the process manager must wait before killing a process after a heartbeat timeout. Default: 5 seconds procm.recovdbfile Storage location of the process manager persistent information. Default:../var/procMRecovery B-34

35 Appendix B for Release 7.4 XECfgParm.dat File s (continued) procm.servfmt Format of the process manager temporary files. Default: PM_%d_%d_input procm.servicesdir Location of the process manager temporary files. Default:../var procmprochealthdfltalmcat product.time This parameter is no longer used. Software time stamp. product.vendor Software vendor name. product.version Software release version number. replicator.portcommchannelrecv Communication port for the replicator. Default: 2974 replicator.portcommchannelsend Communication port for the replicator. Default: 2972 replicator.portdatachannelrecv Communication port for the replicator. Default: 2970 B-35

36 for Release 7.4 Appendix B XECfgParm.dat File s (continued) replicator.portdatachannelsend Communication port for the replicator. Default: 2968 replicator.reconnectinterval Defines the reconnect interval in number of seconds for the replicator during a switchover. Value: Any integer Default: 15 seconds Set this value to 0 for a standalone Cisco MGC. XE.ARUWriteDevice Name of the device from which the alarm relay unit (ARU) expects to read the alarm strings. Example: /dev/null This setting is required if your configuration does not use an ARU. If you do not set this device, the system uses # /dev/tty. Do not change this value unless your configuration uses an ARU. XE.heartBeatRate Heartbeat rate, in seconds, used with an alarm relay unit (ARU). Default: 60 seconds Do not change this value unless your configuration uses an ARU. XE.systemType Indicates the system type for alarm LEDs. NETRA-FT = Sun Netra ft 1800 NETRA = Sun Netra t 1100, t 1120 (internal LEDs, alarm relays) SPARC = Generic box (no alarm relays) SPARC-ARU = Generic box (external alarm relays) Default: SPARC B-36