|
|
TransPath system encompasses much more than the Production platforms that are operating in the field. Many of the subsystems provide support services that are used by customers as part of the overall system. TransPath system provides services to many of these other subsystems. It is important to note that the system architecture is intended to be flexible enough to support both very large and very small customers. Major portions of the system may be distributed over a large geographical area or they may be centralized. TransPath system supports both distributed and centralized architectures equally well.
This section discusses the directory map of the TransPath system software. All procedures required by the UNIX platform are stored here. For example, syslog.conf or /etc/group is in the "utilities" package. Any re-installation of TransPath system has a reduced impact on the platform reducing the amount of time required to reload packages. Included in this section is an overview of the UNIX file directory tree for the TransPath system software along with a brief description of the purpose for each directory. This section is useful for finding files called out in the operating procedures.
During the installation procedures, the user is asked for a directory under which to install the TransPath system (defaulted to "/opt"). The TransPath directory is created under the base directory and everything in the database is put under it. The following layout assumes TransPath is the base directory of the database. For example, if the user accepts the default installation directory, the base directory would be: "/opt/TransPath/".
Within the TransPath Directory, the following subdirectories are created.
TransPath |
|
/bin | Executable programs provided by Cisco Systems that cannot be customized. |
/local | Executable programs provided by Cisco Systems that may be modified by the customer to reflect site-specific requirements. See "Provisioning the Platform." Generally the default values are sufficient. |
/data | MDL source files - If MDL source files are provided, they are located here. |
/etc | TransPath system configuration files - They include all configuration files required for proper operation of the TransPath system. |
/etc/config_lib | TransPath system configuration file library - This is a simple version control system for configuration file changes. |
/lib | MDL object files - These are the executables that are created from the MDL source files and dynamically loaded by the Engine at run-time. |
/var | Subsystem communication and persistent storage area - This directory contains all files and devices providing communications between the various subsystems of TransPath system. Also contains the files providing persistent storage of data for TransPath system. |
/var/log | Subsystem logging area - This directory contains the Command, Alarm, Platform, and the current Dumper logs. |
/var/spool | Dumper Spool Area - This directory contains historic Dumper logs. |
/var/trace | Signal Path Trace Area - This directory contains all trace logs used for conversion analysis. |
This database is a repository that maintains a copy of the configuration data for each managed TransPath system. It stores tailored service packages that have been created by Network Operations personnel. It is also the source of configuration data that is downloaded to each system.
The architecture of the TransPath system application allows the system's configuration to be changed directly in two ways:
The Persistent Database is resident on each TransPath system. This database is comprised of the UNIX files located in /opt/TransPath/etc. The only maintenance required is to ensure that regular backups are performed. This database contains all configuration data necessary to support TransPath system. Programs initialize using the data from this database and it allows programs to recover their last known state in the event of a restart.
The XECfgParm.dat table defines run-time parameter values that all processes running under the XE can access. This file should be tested during the installation process or when system-wide parameters need to be changed. Please note that the TransPath applications must be stopped and re-started to incorporate the new data.
This table does not contain any relationship-style links to other tables. All parameters currently supported in this table are specified and defined below:
Configuration parameters are defined using the following syntax:
<facilityName>.<configparameterName> = <parameterValue>
The facilityName identifies a specific processing subsystems of TransPath system. The following are valid facility names:
| Process Manager Subsystem |
| Engine Subsystem |
| Configuration Manager Subsystem |
| Measurement Manager Subsystem |
| Alarm Manager Subsystem |
| Cisco IOS Channel Manager |
| Cisco IOS Channel Controllers |
| Man-Machine Language Subsystem |
| The Log Dumper Subsystem |
| Execution Environment |
| Failover Daemon (for optional configuration only) |
| default facility |
If no match is found for a facility-specific parameter, then the default facility is used. For example, the following lines in XECfgParm.dat:
| |
| |
The above indicates that all facilities have logging priority set to the Notice level except for the Engine. It has the logging priority set to Debug.
*.platformId | Unique platform identification number (numeric) - Used to allow multiple copies of the platform to run on the same host machine. User can override this value by setting their environment variables. |
*.transpathId | Unique TransPath identification number for the ASN - Consists of 1 to 4 hexadecimal digits. |
*.homeDirRoot | Root directory path for the platform - Relative path names are derived from this root directory. |
*.logPrio | Minimum priority of operational message saved in the logs - Can be changed via the |
*.logDest | Logging Destination to which the operational messages are routed. The following are valid values: |
*.logFileFmt | This is the name of log file used when the If this file does not exist in |
*.logFacility | Default message logging facility to write upon - This should always have the following value: |
*.tablesFile | Name of the file describing all of the tables of persistent objects that can be loaded. |
*.autonomous | Determines whether a process is controlled by the Process Manager. The following are valid values: Default value used during installation should not be changed. Changes may prevent the Process Manager from controlling a process. |
*.runAsDaemon | True/false If true, the process runs as a daemon. These include the following: · detaching from controlling terminal. · becoming a process group leader. · closing all open files including: · opening · setting default directory to · clearing If false, it will not run as a daemon. The default value used during installation should not be changed. Changes may prevent the Process Manager from controlling a process. |
Engine.LCMMdlFile | Universal Call Model MDL object File |
engine.CCMdlFile | Call Context MDL object file |
engine.SysCLIval | Provides a default value which indicates whether CLI Validation processing is to be performed on phone calls. The following are valid values: |
engine.SysPropagateChanAvail | The valid value is the following: |
engine.SysNumTrans | Provides a default value which indicates whether number translation is to be performed on phone calls. The following are valid values: |
engine.SysToneDetect | Provides a default value which indicates whether Tone Detection (i.e., for in-band analogue signals) is to be performed. Valid values are: |
engine.SysMinOverlap | Positive integer indicating the minimum number of dialed digits allowed on a signalling channel that can carry overlap signalling call initiation messages. |
Engine.SysMaxOverlap | Positive integer indicating the maximum number of dialed digits allowed on a signalling channel that can carry overlap signalling call initiation messages. |
IoChanMgr.trace | Unit Test tracing of line and channel state machines - It generates a considerable amount of information to the log so set it to |
IoChanMgr.alarmTimer | Polling period to check alarms in the IO Subsystem. Should be set to zero (the default). This prevents the hardware alarms from being polled. |
IoChanMgr.statTimer | Polling period to collect measurements in the IO Subsystem - Should be set around three seconds (30000 milliseconds). Setting to zero (the default) prevents statistics from being polled. This is not necessary for some I/O cards. Please refer to the Product Release Notes. |
MeasM.evalInterval | Measurement Manager polling interval in seconds. |
procM.minCheckHealthInterval | Minimum interval in seconds, that the |
procM.minCheckHealthTimeout | Minimum interval in seconds that the |
procM.minKillGracePeriod | Minimum interval in seconds that the |
procM.almDwellInterval | Interval in seconds the |
procM.servFmt | Format string used to generate process-specific FIFOs for process management. It has placeholders for platform identification number and process identification number. The default value provided during installation should not need to be changed. |
procM.recovDbFile | Determines dbm files used for |
cfgM.recovDbFile | Determines dbm files used for |
MML.timeout | Default timeout period for commands in milliseconds - If the command takes longer than this to execute the MML session aborts with an error. |
MML.<command>=<time val> | Specific command The default values provided during installation are normally optimal. L MML is configured to abort all commands after four seconds except for |
XE.heartBeatRate | Heartbeat rate in seconds from 5 to 255. Must correspond to the physical setting on the Alarm Relay Unit (ARU). |
XE.ARUWriteDevice | Name of the device where the Alarm Relay Unit (ARU) is expecting input from the platform. |
foverd.fifo1 | Name of FIFO file used by failover daemon for testing purposes. Default value is normally adequate. |
foverd.fifo2 | Name of FIFO file used by failover daemon for testing purposes. Default value is normally adequate. |
foverd.udpPortA | The socket port number used by the failover daemon running on the local system. Should be greater than 1024, and should not conflict with socket ports used by any other applications on the same host. |
foverd.udpPortB | The socket port number used by the failover daemon running on the remote system. Should be greater than 1024, and should not conflict with socket ports used by any other applications on the same host. |
foverd.udpPortAddrA | The socket IP address used by the failover daemon running on the local system to exchange messages with the remote system. |
foverd.udpPortAddrB | The socket IP address used by the failover daemon running on the remote system to exchange messages with the local system. |
foverd.asyncPort | The name of the serial port used to exchange messages with the remote system. |
foverd.pollTimeout | The frequency at which new I/O messages are processed, in milliseconds. The default value is normally optimal. |
foverd.peerCommTimeout | The timeout period after which the remote system is assumed to be unavailable, in milliseconds. Failover will be triggered automatically if there is no communication with the remote system after this timeout period. The default value is normally optimal. Making the timeout value too small will cause false failovers to occur, resulting in possible service interruptions. |
foverd.delayTimeout | The amount of delay offset added when the two failover daemons become too closely synchronized. The default value is normally optimal. |
foverd.pidFile | The file used to store process information used for recovery purposes. The default value is normally adequate. |
foverd.abswitchPort | The serial port used by the local failover daemon to trigger switchover of communication lines when it become the master system. |
foverd.procMCmdLine | The command line used by the failover daemon to start the XE Process Manager. This value will only need to be changed if the TransPath software distribution is installed in a non-standard location. |
foverd.frepldCmdLine | The command line used by the |
|
|