Conference irocz::common_brouters

749.0. "BoD and ISDN problems" by FIRSC1::CASINI () Mon Feb 10 1997 09:13

	Hi all,	
	I've two problems and one question about the BoD configuration
	between two AW90 EI running V2.0-1.

	Here is the configuration of one AW90 EI:

*t 6
Config>list dev
Ifc 0 (Ethernet): CSR 1001600, CSR2 1000C00, vector 94
Ifc 1 (WAN MP): CSR 1001620, CSR2 1000D00, vector 93
        (1 Down Notify Time (sec))
Ifc 2 (ISDN): CSR 1001640, CSR2 1000E00, vector 92
Config>
Config>
Config>net 1
PPP Multilink Protocol user configuration
MP Config>list all

Maximum frame size in bytes = 2048
Encoding: NRZ
Idle State: Flag
Clocking: External
Internal Clock Speed: 0
Transmit Delay Counter: 0
LCP Parameters
Config Request Tries:               20   Config Nak Tries:                   10
Terminate Tries:                    10   Retry Timer:                      3000

LCP Options
Max Receive Unit:                 1800   Magic Number:                      Yes
Authentication Protocol:           PAP
PAP Parameters
Authent Request Tries:              20
Retry Timer:                      3000
Request Timer:                   15000
PAP Ids/Passwords
Local ID:                  system
Local Password:            brouterfi
Remote ID:                 system
Remote Password:           brouterge
CHAP Parameters
Authent Request Tries:              20
Retry Timer:                      3000
Request Timer:                   15000
Repeat Authentication Timer:         0
CHAP Ids/Passwords
Local ID:                  (None)                     
Local Password:            (None)                    
Remote ID:                 (None)                     
Remote Password:           (None)                     
MP Options
Base Links:                          1
Max Links:                           2
BoD threshold:                      70
BoD sample time:                    30
BoD base link line speed:        64000
BoD add link persistence:            5
BoD delete link persistence:        10
Default destination address name:    esaote-ge
NCP Parameters
Config Request Tries:               20   Config Nak Tries:                   10
Terminate Tries:                    10   Retry Timer:                      3000

IPCP OptionsIPCP Compression:                 None
IP Address:      Don't Send or Request
CCP Options
Data Compression disabled
Algorithm: Stac-LZS 
Stac: histories 1
Stac: check_mode SEQ
MP Config>
MP Config>
MP Config>link
Link 101 (MP Dial Circuit): CSR      0, vector 0
MP Config>
MP Config>link 101
Link configuration
Link Config>list
Base net:       2
Destination name:    esaote-ge
Inbound dst name:    * ANY *
Outbound calls       allowed
Inbound calls        allowed
SelfTest Delay Timer = 150 ms
Send Line ID:        NOLink Config>
Link Config>
Link Config>exit
MP Config>
MP Config>exit
Config>
Config>list isdn

Address assigned name             Network Address  Network Subaddress
---------------------             ---------------  ------------------

esaote-ge                         0106591006                           
esaote-fi                         554224696                            
Config>
Config>
Config>
Config>
Config>net 2
ISDN user configuration
ISDN Config>
ISDN Config>list
                                   ISDN Configuration 

Local Network Address Name    = esaote-fi
Local Network Address         = 554224696
Local Network Subaddress      = 

Maximum frame size in bytes   = 2048
Outbound call address Timeout =  180  Retries =   2
Switch Variant                = ETSI NET3
DN0 (Directory Number 0)      = 554224696
DN1 (Directory Number 1)      = 
TEI                           = Automatic
PS1 detect                    = Enabled
No circuit address accounting information being kept
ISDN Config>
ISDN Config>
ISDN Config>exit
Config>
Config>
	

	Problem 1:
	==========

	When the primary link (net 1 64kbps) reaches the throughput of 70%
	the ISDN line goes up and the bandwidth becomes 128 kbps.
	When the throughput falls below 70% the ISDN line goes down, but
	the ISDN port OK Indicator led on the module goes off. From this
	moment it is not possible to use the line anymore until you make a
	t 5 => net 2 => conformance => setup, or a router restart.

	Here is the trace:

*t 2
  GW.001: Copyright 1995-1996 Digital Equipment Corporation
  GW.002: brouterfi, RtAbt Acces EI/MP,  Brouter: 1 Enet 1T1 1BRI,HW=1,RO=1,
          #7188,SW=V2.0-1 Started
  GW.005: Bffrs: 400 avail 400 idle   fair 62 low 80
ISDN.008: Download OK, PUD status (0x0) nt 2 int ISDN/0
ISDN.010: Config ok nt 2 int ISDN/0
ISDN.026: Hndlr inidev() st Config nt 2 int ISDN/0
ISDN.027: Hndlr N_START_RQ nt 2 int ISDN/0
ISDN.025: Start ok nt 2 int ISDN/0
ISDN.003: ConnID 0x90 Status msg cause (0x0:0x0) Power Supply 1 detected ON on nt 2 int ISDN/0
ISDN.003: ConnID 0x36 Status msg cause (0xB:0x4) CCITT line activation achieved on nt 2 int ISDN/0
ISDN.003: ConnID 0xEC Status msg cause (0xA:0x0) CCITT line activation lost on nt 2 int ISDN/0
ISDN.003: ConnID 0x36 Status msg cause (0xB:0x4) CCITT line activation achieved on nt 2 int ISDN/0
ISDN.041: Call for DN 554224696
ISDN.003: ConnID 0x0 Status msg cause (0x3:0xB) Start call alerting on nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x0 FSM st Idle ev ConnInd -> Call_Rxd nt 2 int ISDN/0
ISDN.004: ConnID 0x0 NLS Display Information "Called# 554224696" (cause 0x6:0x4) on nt 2 int ISDN/0
ISDN.004: ConnID 0x0 NLS Display Information "Called# 554224696" (cause 0x6:0x6) on nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x0 FSM st Call_Rxd ev StopAlert -> DataXfer nt 2 int ISDN/0
ISDN.023: ConnID 0x0 Rxd N_STAT_IN ln 0 cause 0x4:0x30 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 35 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 35 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 25 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 30 nt 2 int ISDN/0
.........................................................
.........................................................
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 75 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 38 nt 2 int ISDN/0
ISDN.021: Chn 0 ConnID 0x0 RxD Pkt ln 75 nt 2 int ISDN/0
ISDN.003: ConnID 0x0 Status msg cause (0x5:0x10) NLS Cause Indication on 
nt 2 int ISDN/0
ISDN.033: Chn 0 ConnID 0x0 FSM st DataXfer ev DiscInd -> Idle nt 2 int ISDN/0
ISDN.003: ConnID 0x40 Status msg cause (0xA:0x0) CCITT line activation lost 
on nt 2 int ISDN/0
	
	
	Remarks:
	By using the ISDN line as secondary link with WRS I've tha same trace
	but all works fine (with net 1 and net 3 using PPP datalink). The ISDN
	port Indicator led remains ON.

	Problem 2:
	==========

	When the primary link (net 1 64kbps) reaches the throughput of 0% (I
	disconnected the modem cable from net 1) the ISDN line goes up (as 
	line backup). By reconnecting the modem cable the boundle's throughput
	becomes 128 kbps (the net 1 is added to the boundle), but the ISDN line
	stays up forever even the total throughput is below the 70% of 64 kbps.
	
	Is this normal or not ? My expetation was hang up of ISDN. This to have 
	the line backup feature within BoD functionality.

	Question:
	=========

	Is there any way to monitor the daily use of ISDN (with BoD) ? I mean
	to check how long it is used each day to control the billing.

	Many thanks for your attention.
	Ciao Fabio

    RE: Problem 1:  you need fixkit 1 (v2.0.2), which resolves some
    problems on your type of ISDN switch.
    
    RE: Problem 2:  not sure what is going on there...any BoD experts want
    to comment?
    
    RE: Question about ISDN usage...
    
    There is an 'accounting' feature in the ISDN configuration that can
    track usage, but as I understand it the PTT must send some type of
    billing information for it to work.
    

    Where can I get the fixkit ? (v2.0.2). I looked on pangea
    "/kits/drs_v2/mp/access" but thera are only the v2.0.1
    
    Thanks Fabio

    Any news about "Problem 2" mentioned on .0 ?
    I need to have BoD AND WRS between two AW90s EI.
    
    What about the pointer for the V2.0.2 kit ?
    
    Many thanks for your attention.
    	Regards Fabio

    the fixkit is on haggle:/usr1/users/guest/kits as aw90-v202-funcMP.ldb
    or aw90-v202-funcIP.ldb 
    
    Tim

    
    
    The fixkit v202 solved the problem number 1.
    
    We still have the problem number 2, which is: 
    when the secondary link (the ISDN one) goes on because the primary 
    failed it is never released even when the primary goes back on.
    
    Any BoD expert out there is willing to give us some advise? 
    The configuration is in .0
    
    Regards 
    Fabio

    I think you should raise a CLD about problem number 2.  It should not
    be working that way obviously.
    
    Tim