Home > Lucent Technologies > Communications System > Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual

    Download as PDF Print this page Share this page

    Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.

    Page
    of 458
    							OA&M
    Issue  3  May 1998
    2-11
    asai_cause(1)
    Name
    asai_cause — Logs cause values to stdout
    Synopsis
    asai_cause [-h] [-v] [-t  logtime] [-?] process ids
    Description
    When asai_cause is activated for a process (an ASAI application that is 
    running) and the application receives an ASAI message which contains a cause 
    value from the ECS, the library function asai_rcv() sends an Interprocess 
    Communication (IPC) message containing the necessary information to 
    asai_cause. asai_cause reads the IPC queue, formats the cause information 
    and writes it to stdout.
    asai_cause is activated by including at least one valid process id. Process ids 
    are not checked for validity. asai_cause may be activated remotely or from any 
    login in the system. It is not necessary to be logged in as root to access 
    asai_cause.
    asai_cause prints cause values to stdout. The following information is logged:
    nDate and time
    nProcess id
    nASAI capability name or the hexadecimal operation value (indicates 
    message type)
    nsao_id (formerly known as cluster_id) identifies the particular 
    association for which the message is intended
    nContents of the cause information element (IE) that includes the coding 
    standard and the cause value. The cause value is actually the combination 
    of two fields: a class and a value within the class. The DEFINITY ECS 
    value and the ASAI library interpretation of the cause value is also 
    included.
    The set of PIDs (process identification) being monitored by asai_cause can be 
    changed by reinvoking the command with a new set of PIDs. However, other 
    parameters cannot be changed in this way. The second invocation of
    asai_cause simply changes the PIDs and then exits; it does not start a new 
    logging process. 
    						
    							OA&M
    2-12Issue  3  May 1998 
    The set of input options includes:
    -h
    Causes SIGHUP to be ignored. Default is to exit asai_cause on SIGHUP 
    (hangup).
    -v
    Causes the one-byte hexadecimal operation value from the Facility Information 
    Element (FIE) to reference the ASAI capability rather than include the capability 
    name itself. 
    -t log time
    Specifies a decimal digit string indicating the maximum number of seconds that 
    asai_cause will run. Default is -t 0xffffffff, which is (2**32)-1 seconds.
    -?
    Causes a command usage line to be returned.
    process ids
    Specifies a list of process ids (decimal digit strings) separated by blanks for which 
    cause value logging is to be performed. An empty list turns off cause value 
    logging, but leaves the asai_cause process running. An easier way of 
    terminating cause value logging is to kill the asai_cause process. A maximum of 
    160 process ids may be included.
    Example
    Following is an example of the format used for logging cause values to stdout 
    when the -v option is not included.
    DATE TIME PID CAPABILITY SAO IDDEFINITY 
    ECS    ASAI
    08/27/92 11:35:33 123456 C_3PMC_CONF 4444 CS3/38 C_NETWORK_OUT_OF_O
    08/27/92 11:38:12 123456 C_EN_CAN_CONF 1 CS0/100 C_INVLDIE
    08/28/92 07:49:52 55555 C_3PAD_CONF fffffffd CS0/17 C_USER_BUSY
    08/28/92 09:06:02 55555 C_EN_REP ffffffff CS0/16 C_NORMAL 
    						
    							OA&M
    Issue  3  May 1998
    2-13
    Following is an example of the format used for logging cause values to stdout 
    when the -v option is specified.
    See Also
    asai_trace(1)
    asai_trace(1)
    Shared Resources
    nMessage Queue
    nShared Memory
    Exit Codes
    If asai_cause fails, one of the following exit codes is returned:
    DATE TIME PID CAPABILITY SAO IDDEFINITY
     ECS     ASAI
    08/27/92 11:35:33 123456 0x83 4444 CS3/38 C_NETWORK_OUT_OF_O
    08/27/92 11:38:12 123456 0x94 1 CS0/100 C_INVLDIE
    08/28/92 07:49:52 55555 0xc6 fffffffd CS0/17 C_USER_BUSY
    08/28/92 09:06:02 55555 0x95 ffffffff CS0/16 C_NORMAL
    1 = ftok() failed to determine key 
    2 =  Error in getting shared memory 
    3 =  Error in getting message queue
    4 =  Error in getting a semaphore
    5 =  Attempt to ignore SIGHUP failed
    6 =  asai_cause command-line usage problem
    7 =  Error in attaching to shared memory 
    8 =  Error in setting the value of the semaphore
    9 =  Error in receiving a message
    10 =  Error on attempt to log ASAI cause values 
    						
    							OA&M
    2-14Issue  3  May 1998 
    asai_hb(1)
    Name
    asai_hb — Acknowledges heartbeats for a Node
    Synopsis
    asai_hb [-v] [-?] [-m hostname/IPaddress] [1-8] -n
    Description
    When asai_hb is activated for an ASAI Node it registers itself as a maintenance 
    server for that Node and calls the library function asai_rcv(). If the message 
    received is an ASAI heartbeat, an ASAI heartbeat acknowledgment is sent. 
    If an ASAI heartbeat is not received from the ECS within two minutes, asai_hb 
    sends a heartbeat request to the ECS. If the ECS does not confirm the request, 
    and the -n option has not been specified, the specified Node is brought down 
    using
    ipci_off.
    -v
    Causes asai_hb responses to be printed on the user ’s terminal (stdout).
    -?
    Causes command-line usage information to be printed on the user’s terminal.
    1-8
    1-8 is the Node number that corresponds to the board for which heartbeats will 
    be acknowledged. Node number information can be found in the files 
    /usr/adm/asai/asai_parms
     and /usr/adm/isdn/lan_parms.
    The contents of asai_parms for one installed IPCI board are:
    Node ID for ASAI Node 1 = signal01
    -m
    asai_hb can now be used as a CV/LAN client tool as well as a CV/PC tool. This 
    option has been added to support the use of this tool from a CV/LAN client. The 
    user must specify the IP address or hostname of the CV/LAN server host.
    -n
    Disables the shutdown ipci_off of the link. This option should be used for all 
    LAN type links. It must be the last option specified on the command line. 
    						
    							OA&M
    Issue  3  May 1998
    2-15
    NOTE:
    -m and -n are mutually exclusive.
    Enter the command asai_hb 1 and the process checks for and acknowledges 
    heartbeats immediately for Node number 1.
    Files
    /usr/bin/asai_hb
    /dev/asai/asai
    /usr/bin/ipci_off
    /usr/adm/asai/asai_parms
    /usr/adm/isdn/lan_parms
    See Also
    asai_test(1)
    asai_trace(1) 
    						
    							OA&M
    2-16Issue  3  May 1998 
    asai_log(4)
    Name
    asai_log — Log file for UNIX ASAI
    Description
    This file contains all status and error messages. It resides in the /usr/adm/asai 
    directory.
    The format is:
     time stamp:  program name:  ASCII message newline character
    time stamp
     consists of 12 characters in the format of: yymmddhhmmss. 
    Program name is a 12-character field containing the name of the program 
    (left-justified) that contributed the message to the file. The program name is 
    padded on the right with space characters as needed to fill the field.
    ASCII message consists of 0 through 53 ASCII characters. Every line is ended 
    by a newline character as shown.
    This file should not grow quickly. The programmer can monitor the size of this file, 
    if desired. If this file does get close to the ulimit value, it is renamed 
    old_asai_log and subsequent messages are written to a new asai_log.
    When the system is booted, the old version of this file is renamed 
    old_asai_log. A new asai_log file of 0 length is then created. Subsequent 
    messages are written to this new file. Any previous copy of old_asai_log is 
    removed by this operation.
    Files
    /usr/adm/asai/asai_log
    See Also
    asai(4)
    asai_admin(1)
    ulimit(1) 
    						
    							OA&M
    Issue  3  May 1998
    2-17
    asai_test(1)
    Name
    asai_test — Test connection(s) with the ECS
    Synopsis
    asai_test [-?] [-m hostname/IPaddress] [link]
    Description
    For all ASAI nodes, the connection to the corresponding ECS is tested.
    -m
    This option has been added to support the use of this tool as a CV/LAN client. The 
    user must specify the IP address or hostname of the CV/LAN server host.
    link
    The link that must be tested. All links are tested if this argument is omitted.
    Operation
    For each ASAI node, an ASAI heartbeat request is sent to the corresponding 
    ECS. The response from the ECS is tested for correctness.
    Return Value
    For success, 0 is returned. If an error is detected, 1 is returned.
    Output
    If the response is correct, a success message is printed on stdout. If there is 
    an error, the corresponding error message is printed on stderr.
    NOTE:
    The list of all links is in config_data.
    Files
    /dev/asai/asai
    /usr/adm/asai/config_data 
    						
    							OA&M
    2-18Issue  3  May 1998 
    asai_trace(1)
    Name
    asai_trace — Decodes an ASAI message stream
    Synopsis
    asai_trace [-a] [-c] [-E] [-e] [-f] [-h] [-i] [-m] [-n] [-o] 
    [-q] [-r] [-s] [-v] [-?]
    Description
    asai_trace decodes an ASAI message stream and can be called with 
    command-line options or options can be set using an online help facility.
    -a
    Use short mnemonics (abbreviated mode) 
    -c
    Coding standard information is included 
    -E
    Expect LAN GATEWAY format messages on stdin; for example,
    esai_trace | nawk -f /usr/adm/isdn/bin/xlat.k | asai_trace -E
    -e
    Causes input to be taken from the command esai_trace
    -f
    Creates from 1 to 6 raw hex files (in addition to the trace information). The first file 
    created is rawtrace.out.0. If it overflows, output goes to a second file 
    rawtrace.out.1. If this file also overflows, rawtrace.out.2 is created and 
    so on, up to a maximum of six files. If the sixth file overflows, the entire process 
    begins again and rawtrace.out.0 is overwritten.
    -h
    Displays the help menu
    -i
    Causes input to be taken from the board using the command isdn_trace 
    						
    							OA&M
    Issue  3  May 1998
    2-19
    -m
    Message type information is included 
    -n
    Public or private network and type of user information is included
    -o
    Displays the options help menu
    -q
    Q932 Messages are included 
    -r
    Hex Code is added to the messages (raw mode) 
    -s
    Messages are displayed in split-screen format. Messages from the adjunct appear 
    on one side of the screen while messages to the adjunct appear on the opposite 
    side. Abbreviated mode is forced.
    -v
     Single line per message mode (highly abbreviated)
    -?
    Displays the terse help menu
    Examples
    asai_trace -i
    Trace input directly from the board using isdn_trace
    cat trace.in | asai_trace -r
    Decode trace.in, using raw mode, when a heartbeat is sent to the ECS by 
    asai_test. The trace.in file is created by the command 
    isdn_trace > trace.in &. Output similar to the following is generated:
           ADJ=>sw *0*crv=0004 sec=75.37
    rcv cc 0 07538 90 11 00 08 02 00 04 64 96 1c 09 91 a1 06 02 01 03 02 01 b3 00 00 00 00
    asai_trace -h
    The verbose help menu is displayed. 
    						
    							OA&M
    2-20Issue  3  May 1998 
    Files
    /usr/adm/isdn/bin/asai_trace
    /usr/adm/isdn/bin/isdn_trace
    /usr/adm/isdn/bin/esai_trace
    See Also
    asai_trace(1) 
    isdn_trace(1) 
    						
    All Lucent Technologies manuals Comments (0)

    Related Manuals for Lucent Technologies DEFINITY Enterprise Communications Server Release 6 CallVisor PC ASAI Instructions Manual