Logging Configurations Flashcards
verbose
debug log level option for application properties verbose = all/standard/interaction/trace/debug/all or all =
connection
All connection are TCP/IP based and application communicate across IP networks on TCP ports
Common Connection: Configuration Server
The Configuration server is the source of all configuration data such as the options, DNs, connections. Applications must be connected to the configuration server in order to start. The command line to connect to Config Server –host -port -app .
The URS, T-server, and Stat Server retrieve the configuration data to get the information on the options, DNs to registered, and connections to other applications. This is the first thing the application will do and retrieve these configuration data when first startup.
Connection Issue in Configuration Server
Application process keeps running and reconnects every 5 seconds are indicators of issue with the Config server. Logs not generated is also another concern and if this is the case then the application is not working.
Troubleshoot method such as output through console screen and redirect stderr and stdout to a file
Common Connection: License Manager
License Manager(FlexM)
Controls the licensing and T-sevrer/URS must connect and have licenses to start.
Configuring License Manager connection
Command line –l parameter EX. Ur_server.exe -host GEN01 –port 2020 –app URS –I 7260@GEN01
Option License-file in [license] section
[license]
License-file = 7260 7260@GEN01
License Requirements URS
Router_seats – controls number of targets URS can monitor
Router_ha_option – Required for URS Hot Standby redundancy
License Requirements T-Server
Tserver_sdn – controls number of DNs T-server clients can monitor
Tserver_iscc – rquire for Multi-Site Transfer functionality
Cti_ha_option – required for T-server Hot-Standby redundancy
ADDP
Periodically pings idle connections in order to detect network problems and outages at the remote end.
Bi-directional failure detection where both server and client are able to detect the failure
ADDP – Advanced Disconnection Detection Protocol
ADDP Trace Format
ADDP messages start with –A and the next character describes the message type.
Upper case is a request, lower is a response The P in the example means polling message EX: -AP[1] --4
The [1] in brackets indicates the polling id of 1 while other messages type have different arguments.
'' indicate it was sent The next would be a number that indicates the socket number to which a message was sent or received There may also be a message timestamp that are omitted in responses
Connection issues with License Manager
Application(T-server, URS) is unable to connect to FlexM due to various reason such as network issues, incorrect parameters, or the FlexM is not running.
EX: License failed, reason ‘GLMR_LICEMSE_SERVER NOT_AVAILABLE’
Application such as the URS and T-server will need to connect to the License Manager and if it fails to do so then it will terminate. The T-server will make one attempt only while the URS will do a number of times before it terminates.
SCS
The SCS receives the information from the LCA on the status of the application. It also receives event messaging on the message server because it is subscribed to it and will receive notification when a subscribed event is received. When SCS receives notification from the messaging server that an application state has change it can respond to it by failing over to backup, restarts, execution of OS scripts, and generate email alarms.
Message Server
The message server processes event messaging for the purposes of inserting logging into the Log Database and the input of alarm detection in Management Layer.
Local Control Agent
LCA monitors all Genesys applications including third party ones and reports the current status of these application such as T-server and URS to the Management Layer. LCA is also responsible for starting and turning off the applications.
Incorrect Application name of mismatch application type
Cannot connect Config Server at GEN01:2020, reason application name is unknown. DBID unknown
Cannot Resolve Host Name for Configuration Server
error: Cannot resolve name ‘BAD HOST NAME’
Cannot connect to Config Server at BAD HOST NAME, reason CFGServerNotFound
