[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::decnis

Title: DEC Network Integration Server (DECNIS)
Notice:Please read note 1 to use this conference effectively
Moderator:MARVIN::WELCH
Created:Wed Sep 18 1991
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3660
Total number of notes:15082

3532.0. "llc2 to lapb truncates CALLED DTE?!?" by MLNORO::MALACRIDA () Tue Feb 04 1997 04:34

 I've set up a WAN-LAN X.25 relay between a DECnis 

          Name = DEC Network Integration Server 600 ,
          Version = "V3.1.2"

and a DU machine with DECnet/OSI 

          Type ........  = DECnet/OSI for Digital UNIX ,
          Implementation = "DECnet/OSI for Digital UNIX V3.2A-0 
                           (Rev. 23.19); Fri Sep 15 13:21:53 EDT 1995"

and X.25 for DU version 2.0.

 Everything seems ok (LLC2 dte up and running, the filter can relay the call
 coming from the the Alpha machine) but when the call request comes out
 on the LAPB dte the CALLED DTE field is horribly truncated, as per the trace
 below.
 

-----------+----+-----+<--------Packet-------->+--------------------------------
    Time   |Evnt|Data |Chn Q Type     P    P   |Data
hh mm ss cc|    |Size |    M         R/S  R/S  |
-----------+----+-----+<---------------------->+--------------------------------
17:09:31.74|  Tx|   24|07F   CALL              |Called DTE 00
                      |                         Calling DTE 000012003300000
                      |                         Facilities 42 07 07 43 02 02
                      |                         Data 01 00 00 00|
                      |                        |
                      |                        |
17:09:31.75|Rx  |    5|07F   CLR   C=13 D=43   |
17:09:31.76|  Tx|    3|07F   CLRC              |
 
 As far as the call request appears at LLC2 dte level, this is what the 
 trace says:

-----------+----+-----+<--------Packet-------->+--------------------------------
    Time   |Evnt|Data |Chn Q Type     P    P   |Data
hh mm ss cc|    |Size |    M         R/S  R/S  |
-----------+----+-----+<---------------------->+--------------------------------
17:08:15.26|Rx  |   27|010   CALL              |Called DTE 00001200710000
                      |                         Calling DTE 987654321
                      |                         Facilities 42 07 07 43 02 02
	              |                         Data 01 00 00 00|

 A similar problem is described in note 2836, but in my case, even with LLC2
 dte address of less then 11 digit (I tried 10,9,8 ... then I stopped the
 count-down) the result is exactly the same.

 Any help appreciated.

 giovanni


 ------------- LLC2 dte and LAPB dte definitions at DECnis -----------------

Node dns600 X25 Protocol DTE dte-to-snagtw
at 1997-02-03-18:11:24.803+01:00Iinf

Characteristics

    Inbound DTE Class                 = llc2
    Profile                           = "ISO8881"
    X25 Address                       = 12345678
    Interface Type                    = Negotiated
    Description                       = "DECX25Gateway 500/100V1.0"
    Maximum Active Circuits           = 512
    Maximum Clear Attempts            = 0
    Maximum Reset Attempts            = 1
    Maximum Restart Attempts          = 1
    Call Timer                        = 200
    Clear Timer                       = 180
    Interrupt Timer                   = 180
    Reset Timer                       = 180
    Restart Timer                     = 180
    Link Service Provider             = LLC2 SAP sap-0 Link decnis-to-snagtw
    Outgoing List                     = 
       {
          [1..127]
       }
    Extended Packet Sequencing        = False
    Maximum Throughput Class          = 48000
    Minimum Throughput Class          = 75
    Maximum Packet Size               = 1024
    Default Packet Size               = 128
    Minimum Packet Size               = 128
    Maximum Window Size               = 7
    Default Window Size               = 2
    Minimum Window Size               = 2
    CCITT Version                     = 1984
    Incoming List                     = 
       {
          [1..4095]
       }
    Segment Size                      = 64




Node dns600 X25 Protocol DTE DTE-3-0
at 1997-02-03-18:12:32.673+01:00Iinf

Characteristics

    Inbound DTE Class                 = TELENET
    Profile                           = "TELENET"
    X25 Address                       = 00001200330000
    Interface Type                    = DTE
    Description                       = "DECX25Gateway 500/100V1.0"
    Maximum Active Circuits           = 512
    Maximum Clear Attempts            = 0
    Maximum Reset Attempts            = 2
    Maximum Restart Attempts          = 2
    Call Timer                        = 200
    Clear Timer                       = 180
    Interrupt Timer                   = 0
    Reset Timer                       = 180
    Restart Timer                     = 180
    Link Service Provider             = LAPB Link DTE-3-0
    Outgoing List                     = 
       {
          [1..127]
       }
    Extended Packet Sequencing        = False
    Maximum Throughput Class          = 48000
    Minimum Throughput Class          = 75
    Maximum Packet Size               = 1024
    Default Packet Size               = 128
    Minimum Packet Size               = 128
    Maximum Window Size               = 7
    Default Window Size               = 2
    Minimum Window Size               = 2
    CCITT Version                     = 1984
    Incoming List                     = 
       {
          [1..4095]
       }
    Segment Size                      = 64

       
T.RTitleUserPersonal
Name
DateLines
3532.1nobody out there ?MLNORO::MALACRIDAThu Feb 06 1997 03:382
    
    
3532.2Fixed 6 months later ...MARVIN::CARLINIThu Feb 06 1997 05:5324
> A similar problem is described in note 2836, but in my case, even with LLC2
> dte address of less then 11 digit (I tried 10,9,8 ... then I stopped the
> count-down) the result is exactly the same.

I tracked that one down and it was CFS.35385. That fix first went into V3.1.7.
The problem was caused by the code using a pointer to a template regardless of
whether one existed or not. The effects are, as you can imagine, moderately
random so your symptoms don't surprise me.

The quick and dirty check is to make sure that you specify a valid template on
the relay client - the template doesn't actually need to do anything, it just
has to exist and be specified. You should ensure that you have a template on
every relay client if you continue to run V3.1.2 - the code *will* use something
so you had better make it use something reasonable!

This is just a short term fix to verify that your problem is what I think it is.
If this works, please upgrade to V3.1-8 (or V3.1-9 which will be available
fairly soon now - days rather than weeks - and which has other relay fixes which
you may need).

If the workaround does not work, please log an IPMT against DECnis and include a
reference to this note stream as well as a pointer to the DECnis NCL scripts.

Antonio