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

							Issue  3  May 19982-1
2
OA&M
ASAI operation, administration, and maintenance (OA&M) consists of a few tasks 
that have to be performed at regular intervals and/or under certain conditions.   
						

							OA&M
2-2Issue  3  May 1998 
The ASAI Log File
The ASAI log file, asai_log, is stored in /usr/adm/asai and can be examined 
using vi or cat.
Each time the UNIX system is started, the existing log file is moved to 
old_asai_log and a new log file is created. This old_asai_log file is located 
in the same directory as asai_log. In addition, if asai_log becomes “full” 
(close to ulimit in size), it is moved to old_asai_log. Note that this overwrites 
an existing old_asai_log.
You can split or copy a log file; however, only root has write permission in the 
/usr/adm/asai directory. Therefore, you will have to use a directory in which 
you have write permission to execute the split or cp command. (The ASAI 
Administration menu provides access to UNIX system commands, so you can do 
this by escaping from the menu, if you prefer.)
The log file contains entries consisting of a date and time stamp followed by a 
colon, the name of the ASAI process that wrote the message, another colon and 
the message. The message tells you whether or not the process executed 
successfully.
Figure 2-1. An ASAI Log File
In the sample shown above, the first 12 characters represent a date and time 
stamp. The date is in the form 
yymmdd; the time is in the form hhmmss, based on 
a 24-hour clock. Thus 11:30 p.m. appears as 2330. 
Following the date and time stamp, comes the name of an ASAI process, 
preceded by a colon (asai_admin in the sample). Another colon precedes the 
message. Messages longer than 53 characters are carried over to the next line as 
shown in lines 2 and 3 in Figure 2-1. 
910318165042:  asai_admin:  ASAI administration daemon has started.
910318165042:  asai_admin:  Push of FEL onto /dev/isdn/ipci/signal01 
succeeded.
910318165042:  asai_admin:  Link of /dev/asai/asai with 
/dev/isdn/ipci/signal. 
910318165042:  asai_admin:  101 succeeded.
910318165042: asai_admin:  ASAI stack setup was successful. 
						

							OA&M
Issue  3  May 1998
2-3
OA&M Manual Pages
This section contains manual pages for the commands and files that comprise 
ASAI Operations, Administration and Maintenance (OA&M). For ease of 
reference, commands, and files appear in alphabetical (ASCII) order.
In this section (1) corresponds to commands, (4) refers to the files, and (7) 
corresponds to the devices and pseudo-devices.
Command name prefixes and suffixes imply the following:
admin(7)               ipci_off(1)
asai(4)                ipci_on(1)
asai(7)                ipci_stat(1)
asai.Date(4)           ipci_test(1)
asai.Name(4)           ipci_ver(1))
asai_admin(1)          isdn_alarm(1)
asai_cause(1)          isdn.Date(4)
asai_hb(1)             isdn_l1_r(1)
asai_log((4)           isdn_l2_r(1)
asai_test(1)           isdn.Name(4)
asai_trace(1)          isdn_trace(1)
asai_ver(1)            lan_status(1)
boot.bin(4)            log_msgs(4)
cmd(7)                 link_alarm(1)
command(7)             link_offline(1)
esai_alarm(1)          link_restart(1)
esai_trace(1)          link_status(1)
ipci_admin(1)          pcisdn.bin(4)
ipci_init(1)           signal(7) asai_Commands related to the kernel ASAI protocol stack or the 
ASAI library
ipci_Commands related to the ipci device drivers
isdn_Commands related to the BRI link between the BRI board 
and the ECS
.binCommands related to software that is downloaded 
(‘‘pumped”) to the BRI board
esai_Commands related to the CallVisor LAN GATEWAY interface
linkCommands related to the CallVisor LAN GATEWAY interface 
						

							OA&M
2-4Issue  3  May 1998 
admin(7)
Name
admin — IPCI and LAN GATEWAY Streams Device Driver Communication File
Description
The admin file allows communication between the ipci_admin(1) program, the 
IPCI streams device driver and the LAN GATEWAY streams module. The IPCI 
streams device driver communicates with the IPCI board and with software on the 
board.
This file is meant to be used only by the ipci_admin(1) program. Information 
flows only one way from the IPCI device driver to the ipci_admin(1) program.
This file will have the same major device number as the signal(7) and 
command(7) files. Its minor device number is 0.
Files
/dev/isdn/ipci/admin
/dev/esai/admin
See Also
ipci_admin(1)
command(7)
cmd(7)
signal(7) 
						

							OA&M
Issue  3  May 1998
2-5
asai(4)
Name
asai — Start ASAI administration
Synopsis
asai
Description
asai is a shell script that starts the ASAI administration daemon process, 
asai_admin(1), located in /etc/idrc.d.
Operation
The asai program is executed once per machine boot in the multiuser init level 2. 
The name of the log file (asai_log) is changed to old_asai_log. The 
administration daemon asai_admin(1) is then started. When this is done, the 
standard error device is defined as /dev/console for asai_admin(1).
Files
/usr/adm/asai/asai_log
See Also
asai(7)
asai_admin(1)
asai_log(4) 
						

							OA&M
2-6Issue  3  May 1998 
asai(7)
Name
asai — ASAI communication file
Description
This file allows communication with the ECS via the ASAI library functions. It is 
meant to be opened by the ASAI library function asai_open().
This file is created when the software is installed.
Files
/dev/asai/asai
See Also
asai_admin(1) 
						

							OA&M
Issue  3  May 1998
2-7
asai.Date(4)
Name
asai.Date — Date file for UNIX ASAI
Description
This file contains the date and time the software for ASAI product was 
manufactured. 
Files
/usr/adm/asai/asai.Date 
						

							OA&M
2-8Issue  3  May 1998 
asai.Name(4)
Name
asai.Name — Name file for UNIX ASAI
Description
This file contains the name of the ASAI software package. The content of 
the file is:
Lucent Technologies CallVisor ASAI 
Files
/usr/adm/asai/asai.Name 
						

							OA&M
Issue  3  May 1998
2-9
asai_admin(1)
Name
asai_admin — Administer ASAI file
Synopsis
asai_admin
Description
asai_admin sets up the protocol stack for the ASAI device file and sends 
necessary parameters to the ASAI provider.
Operation
The asai_admin program is executed once per machine boot. It is started by 
asai(4) and becomes a daemon process.
This program has two tasks.
a. To perform the necessary streams operations with UNIX kernel module(s) 
and the signal streams to complete the ASAI streams protocol stack.
b. To condition each protocol stack with the board node ID value and the ECS 
protocol value.
The protocol stack can be used after asai_admin has built the protocol stack. 
When asai_admin has built the stack, the /dev/asai/asai file is available for 
use.
The ASAI stream file is always kept open by asai_admin.
Messages
Messages (status and error information) are written to the asai_log file. Some 
of these messages may come from the ASAI provider streams module.
Exit Codes
This program, if it exits, exits with a code of 1. Since this program is meant to be 
run as a daemon process, the exit code is meaningless. 
						

							OA&M
2-10Issue  3  May 1998 
Files
/dev/asai/asai
/usr/adm/asai/asai_log
See Also
asai(4)
asai(7)
asai_admin(1)
asai_log(4)