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

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

							OA&M
2-42Issue  3  May 1998 
isdn_11_r(1)
Name
isdn_11_r — Restart layer 1 and layer 2
Synopsis
isdn_11_r
Description
isdn_11_r will cause layer 1 and layer 2 to be restarted.
Operation
isdn_11_r is invoked as a single command with no options; the user is 
prompted for a board number from 1 to 4.
isdn_11_r is a script file that invokes ipci_on and ipci_off for the specified 
board. The diagnostics for isdn_11_r are the same as those for ipci_off and 
ipci_on and the exits codes are those of ipci_on.
See Also
ipci_on(1)
ipci_off(1)
asai_hb(1) 
						

							OA&M
Issue  3  May 1998
2-43
isdn_12_r(1)
Name
 isdn_12_r — Restart layer 2
Synopsis
isdn_12_r [-b1...-b4] [-e] [-?]  
Description
isdn_12_r sends a layer 2 reset to the board specified by the -b parameter. If 
layer 1 and layer 2 are both up, layer 2 will be taken down then brought back up. If 
layer 2 is already down, an attempt will be made to bring it back up.
-b
Restarts the level 2 link for the specified board, where =1...4, the 
default is -b1.
-e
Displays the exit codes list shown below
-?
Displays the terse help menu
Exit Codes
If isdn_12_r fails, one of the following exit codes is returned:
 0 =  The reset occurred per request
-1 =  Failure due to inadequate memory
-2 =  Open stream failure
-3 =  Failure to send message(s) to board
-4 =  Failure to receive message(s) from board.
-5 =  Time-out while waiting to receive a message 
						

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

							OA&M
Issue  3  May 1998
2-45
isdn_trace(1)
Name
isdn_trace — Trace IPCI device driver messages
Synopsis
isdn_trace
Description
isdn_trace writes the kernel protocol stack messages to stdout. This is a 
general-purpose diagnostic tool. Only one of its outputs is the actual message 
traffic to and from the PC/ISDN board. The message trace has the following 
general format:
       
The following table explains the format.
Received messages (those coming from the ECS) usually have rcv cc in the 
function field. 
cc refers to the courtesy copy buffer which is a general-purpose 
board to the driver-transfer buffer.
Table 2-2. Format of isdn_trace-Generated IPCI Device Driver Messages
Mnemonic Description Example
 message time stamp number 15273
 name of module generating the entry IPCI
QP
Klog
 name of function handling the 
messagercv cc
gviSendSignal
 /
 starting byte number 0
12
 message traffic has the value
 MSG_TRACE in this field. Only 
message traffic is useful.MSG_TRACE

						

							OA&M
2-46Issue  3  May 1998 
Transmitted messages (those going to the IPCI board and then the ECS) usually 
have a mnemonic function, for example, gviSendSignal.
The function name is separated from the starting byte number by a slash ( / ).
The starting byte number indicates the byte number of the beginning (left most) 
byte of the hex field. The first line of a message has a byte number of 0. The 
second line has a number greater than zero (usually 12) and so forth for each 
additional line of the same message. The next message will have a byte number 
of 0 for the first line.
The diagnostic field indicates the purpose of the entry. Only trace entries with a 
diagnostic field value of MSG_TRACE are useful.
The driver QP frequently writes diagnostic messages. These messages are 
normal and can be ignored. Periodically, the kernel-reporting mechanism klog 
also writes entries. These can also be ignored.
Examples
 >isdn_trace > trace.in &
Turn on trace and send the output to the file trace.in.
tail trace.in
Display the end of the trace.in file. When a heartbeat was sent to the ECS 
using the command asai_test, output similar to the following is generated:
15273 IPCI gviSendSignal/0 MSG_TRACE_LINK: 95 11 00 08 02 00 02 64 96 1c 09 91
15273 IPCI gviSendSignal/12 MSG_TRACE: a1 06 02 01 03 02 01 b3 00 00 00 00
15273 IPCI rcv cc/0 MSG_TRACE: 90 11 00 08 02 00 02 64 96 1c 09 91
15273 IPCI rcv cc/12 MSG_TRACE: a1 06 02 01 03 02 01 b3 00 00 00 00
15273 QP qp_rsrv/515 freeing unrecognized message of size 0x2
15273 QP qp_rsrv/516 msg[0]=0x8, msg[1]=0x1
Bugs
The kernel mechanism used by the device driver does not guarantee message 
order or integrity. Therefore, a sequence number is placed on each message by 
the IPCI device driver to allow detection of missing or out-of-order messages.
Turning on the message trace facility causes an additional system load. 
Sometimes the load is significant. 
						

							OA&M
Issue  3  May 1998
2-47
Files
/usr/adm/isdn/bin/isdn_trace
/usr/adm/isdn/bin/asai_trace
See Also
asai_trace(1) 
						

							OA&M
2-48Issue  3  May 1998 
lan_stat(1)
Name
/usr/adm/isdn/bin/lan_stat — Print Status of LAN Gateway links
Synopsis
lan_stat [-n] linkNo | [-a]
Description
If n linkNo is specified, a status report is printed only for that link. Otherwise, a 
status report is given for all LAN gateway links. The report is printed to stdout. 
Lan_stat with no arguments specified will print the status for only those LAN 
Gateway links that are administered. 
If the -a option is specified, a long form of status is reported for all possible LAN  
Gateway links. The long form contains the following information:
Table 2-3. Long Form Status Values
Link The LAN Gateway link number. Possible values are 1 to 8.
Dest The Hostname of the ASAI-E board with which the link will 
connect.
Type The type of link (LAN or ISDN) should always be LAN.
Status The status of the link (numeric value in braces).
Num Retry The number of times the LAN Gateway link has attempted to 
connect to the ASAI-E board.
time to Retry The number of seconds until the next connect attempt will be 
made.
Link Fd The file descriptor of the socket connection for the LAN link.
MUX Fd The file descriptor of the multiplexor for the LAN link.
TLI Fd The file descriptor of the TLI to TCP connection. 
						

							OA&M
Issue  3  May 1998
2-49
The short form (default) prints only Link, Dest, and Status.
See Also
ipci_stat(1) 
link_status(1)
Table 2-4. Common Status Values
TalkingThis indicates “Layer 2” connectivity to the ECS.
TLiFailure This indicates that the PC is unable to talk to the ASAI MAPD. It 
could be a LAN problem or the MAPD could be down or 
disconnected from the LAN.
BRiDown This indicates that the CallVisor PC can connect to the MAPD 
via the LAN, but the MAPD is not communicating with the 
DEFINITY ECS.
InvalidClient This status indicates that the MAPD board has not been 
administered to communicate with this CallVisor PC LAN link.
offline This status indicates that this LAN link was put offline via the 
link_offline(1) OA&M command. 
						

							OA&M
2-50Issue  3  May 1998 
link_alarm(1)
Name
/usr/bin/link_alarm — Suspend or resume alarms for a LAN link
Synopsis
esai_alarm(1)
Description
Link_alarm is a shell script that verifies that the specified link is a LAN link 
before invoking esai_alarm(1) to suspend or resume alarms.
See the manual page for esai_alarm(1)) for command line options.
See Also
esai_alarm(1)
isdn_alarm(1)