UNIX utilities (syslog,bootp,eft,bricktrace)

This note is not a complete reference and might have some faults.
We would appreciate corrections, which could be sent to support@bintec.de.

1. configure a UNIX syslogd (example: SunOS)
2. setup (LAN ip address) with bootp (example: SunOS)
3. using the remote CAPI with EURO FILE TRANSFER
4. using the remote CAPI with BRICKTRACE

1. configure a UNIX syslogd (example: SunOS)
------------------------------------------------------------------------------
BRICK:
------
biboAdmLogHostTable
-------------------
-> define syslog hosts

inx Addr(*rw) Level(-rw) Facilities(rw)

00 192.54.53.5 debug 0x0
| |-> 0: every message of
| the configured
| level is logged
|-> IP address or hostname where the syslog messages are sent to

debug is the highest level, so every message with lower levels are also logged.

biboAdmSyslogTable
------------------
-> shows syslog entries on the BRICK
(to show the whole entry you should set more columns -> brick> u 200)

inx TimeStamp(ro) Level(ro) Facility(ro) Message(ro)

01 01/01/70 0:36:15 info Accounting "ISDN: ,00:36:14,
02 01/01/70 0:36:15 info isdn "PPP: dialup2 > 0

configuration SunOS:
--------------------
/etc/syslog.conf
----------------
local0.debug /var/adm/box-debug0
...
local6.debug /var/adm/box-debug6
local7.debug /var/adm/box-debug7

REMARK: The SunOS syslogd only knows level 0 - 7:
local0-7 Reserved for local use.
SunOS: man syslog.conf, man syslogd
reread the configuration: kill -1 `cat /etc/syslog.pid`

/var/adm/box-debug0
-------------------
e.g.:
May 8 14:23:32 brick2.BinTec.DE ISDN: 08.05.1996,12:23:32,12:23:32,0,36,47,3,3,0,I,8,219,7/0,9F,0
May 8 14:28:38 brick2.BinTec.DE ISDN: 08.05.1996,12:28:06,12:28:38,32,1170,1899,41,44,0,I,8,212,7/0,90,0

(-> with the isdnAccountingTemplate( rw):
"%S,%s,%r,%d,%y,%Y,%g,%G,%c,%n,%Z,%T,%i,%u,%L" -> software reference manual)

/var/adm/box-debug6
-------------------
e.g.:
May 8 14:23:31 brick2.support.BinTec.DE PPP: incoming call from <219>
May 8 14:23:31 brick2.support.BinTec.DE PPP: accepted: call not identified by number
May 8 14:23:32 brick2.support.BinTec.DE PPP: ? PAP/CHAP authentication failure
May 8 14:23:32 brick2.support.BinTec.DE PPP: ? < 0 21 35 7
May 8 14:28:05 brick2.support.BinTec.DE PPP: incoming call from <212>
May 8 14:28:05 brick2.support.BinTec.DE PPP: accepted: call identified for interface 10001
May 8 14:28:37 brick2.support.BinTec.DE PPP: adonis < 0 1429 1723 7

/var/adm/box-debug7
-------------------
e.g.:
May 8 14:21:28 brick2.support.BinTec.DE bridged: no license

To Trace syslog packets with etherfind:
---------------------------------------
Ethernet-Trace on SunOS: etherfind dstport 514 dst adonis
| |-> IP address or hostname
| where the syslog messages
| go to
|-> destination port of the syslogd

2. setup (LAN ip address) with bootp (example: SunOS)
------------------------------------------------------------------------------

The MAC address of the brick you get with:
------------------------------------------
ifstat
-------------------------------
-> shows the MAC address of the ethernet module (here: PhysAddress of en1)

ifstat
Index Descr Ty Mtu Speed St Ipkts Ies Opkts Oes PhysAddress
01000 en1 6 1500 10M up 3079 0 3873 1 00:a0:f9:00:01:3c
...

CONFIGURATION FILE of BOOTPD:
-----------------------------
# Example /etc/bootptab: database for bootp server (/etc/bootpd).
# Blank lines and lines beginning with '#' are ignored.
#
# Legend:
#
# first field -- hostname
# (may be full domain name)
#
# ha -- hardware address
# ht -- hardware type
# ip -- host IP address
# sm -- subnet mask
#
# Be careful about including backslashes where they're needed. Weird (bad)
# things can happen when a backslash is omitted where one is intended.
# example for a brick:
brick1:\
:ht=ether:\
:ha=00a0f9000150:\
:ip=192.54.53.8:\
:sm=255.255.255.128:

REMARK: :1: will lead to 01 in the ha STRING)

start the BOOTPD with:
-----------------------
1. bootpd -s or
2. in your /etc/rc.local file for SunOS or within /etc/rc2.d or your systems
boot files.

3. using the remote CAPI with EURO FILE TRANSFER
------------------------------------------------------------------------------
example: LAN ip address of the brick: 192.54.53.8

UNIX   I   Brick
Workstation   S    
with   D    
Eurofiletransfer   N    
192.54.53.5       192.54.53.8



example session: connecting to BinTec's public EFT server:
----------------------------------------------------------
root> export CAPI_HOST=192.54.53.8
root> eft -i
BIANCA/ISDN EuroFileTransfer
eft> ?

BIANCA/ISDN Eurofiletransfer Client

Commands are:
connect [<controller>=]<telephone number> [<username>[/<password>]]
create <new directory>
cd <path>
delete <filename>
dir <filemask>
disconnect
help
info
load <remote filename> [<local filename>]
pwd
rename <old remote filename> <new remote filename>
save <local filename> [<remote filename>]
status [on|off]
quit

eft> connect 09119673263
connect: Ok
Connected with: 09119673263 BIANCA ISDN EFT BinTec Suppo
eft 09119673263 >dir
dir: Ok
##
0 incoming/
0 faqs/
0 software/
0 brick/
0 docu/

eft 09119673263 >cd brick/sun
cd: Ok
#
Changedir ok
eft 09119673263 >cd: Ok
eft 09119673263 >##
122880 bricktra
40960 eft
114688 eftd
775 eft.cf
3915 eftd.cf

...

ATTENTION: you always have to use the full path relative to the home directory
of your eft account.

The complete ISDN number of BinTec's public EFT server is +49 911 9673 263
at the moment.

4. using the remote CAPI with BRICKTRACE
------------------------------------------------------------------------------
usage: bricktrace [-h23aeFpitx] [-T <tei>] [-c <cref>] [-r <cnt>] [-H <host>] [-P <port>] <channel> <unit> <slot>
-h hexadecimal output
-2 layer 2 output
-3 layer 3 output
-a asynchronous HDLC (B-Channel only)
-e ETS300075 (EuroFileTransfer) output (B-channel only)
-F FAX (B-Channel only)
-p PPP (B-Channel only)
-i IP output (B-Channel only)
-t ascii text output (B-Channel only)
-x raw dump mode
-T set tei filter (D-Channel only)
-c set callref filter (D-Channel only)
-r<cnt> receive only cnt bytes
-H<host> specify trace host
-P<port> specify trace tcp port (default: 7000)

<channel> 0 = D-Channel
1..31 = Bx-Channel
<unit> 0..1
<slot> 1..2

Example:
--------
LAN ip address of the brick: 192.54.53.8
You could set the trace host variable (IP address of the BRICK), e.g.:
export TRACE_HOST=192.54.53.8
or you can use the bricktrace option -H<host>
(e.g.: bricktrace -h23i -H 192.54.53.8 0 0 2)

bricktrace -h23i 0 0 2
| | |- slot .. 1. digit in isdnIfIndex from the isdnIfTable
| | physical slot in the brick
| |--- unit .. 2. digit in isdnIfIndex
| phys. Port on the card, e.g.
| for double S0: 0 or 1
|----- chan .. 4. digit in isdnIfIndex
0 = Dchannel, 1 = B1channel, ..
isdnIfIndex 2000
||||- chan
|||-- ?
||--- unit
|---- slot

when bricktrace connected successfully, you will see the following message:
bricktrace: Connected to 192.54.53.8(7000)
| |-> port for the remote CAPI
|-> IP address of the brick

isdnIfTable
-------------------------------------------
-> check if the ISDN autoconfiguration was successful (AutoconfigState is done)
show the slot/unit to use for tracing

inx Index(*ro) Description(ro) Layer1State(ro)
BchannelControl(ro) ActivationRequest(rw) Mode(rw)
TimerT3(rw) UsePowerDetector(rw) NumberOfChannels(ro)
Timeouts(ro) Activates(ro) Deactivates(ro)
AutoconfigState(rw) Autoconfig(rw)

00 2000 "bri2-0" f7
controlled nooperation te
5000 use 3
0 1 0
done on

isdnIfAutoconfigState: (readwrite) start(1),running(2),done(3)
|-> rerun ISDN stack autoconfiguration

 

Wichtige Links

FAQ-Indexseite
 
If you have comments or suggestions, send email  at support@BinTec.DE