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

Conference ozrock::x25_osf

Title:Proudly built by the engineers of NaC Australia
Moderator:DELNI::MUGGERIDGE
Created:Tue Oct 13 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:908
Total number of notes:3829

869.0. "Urgent ! Pls help ! UNIX<---X25--->NOKIA DX200" by HGOM11::LKLEE () Wed Feb 19 1997 14:16

Hello,

I need to setup connection between our UNIX system and  Nokia DX200 switch
using  x.25 protocol in China.  Since the Nokia people here is not experience 
in this kind of connection, can anyone share some of your experience with me ?

The Nokia switch will use x.25 protocol communicate with Digital UNIX
thru decnis 500 as shown in the below diag.  Our side is configured as
DCE mode, Nokia side is configured as DTE mode.  A pair of modem is 
placed between these two systems for electrical isolation.     




    +------------------+      +----------+              +---------+
    |                  |      |          |              |         |
    | digital UNIX     |      | decnis   |DCE        DTE| NOKIA   |
    | decnet /osi      |      |  500     +--------------+ switch  |
    | X25 software     |      |          |              |         |
    +-------+----------+      +-----+----+              +---------+
            |                       |
    ========+=======================+======

    FTAM is used for transfering files between unix and nokia system.


    
My current problem is the X.25 can not up and running.

I think the problem is unmatched network profile.  Please advise which network
profile should be used for communication with Nokia DX200 switch.  The Nokia
people can't find out which profile should be used.  The following is the 
parameter list  given by the Nokia people :

   *******************************************************************

LEVEL 2 PARAMETERS:

L2 TIMER T1 : 6 SECONDS			l2 BITS IN FRAME: 1024 BITS
L2 TIMER T2: NOT IN USE 		L2 RETRY COUNT:   10 TIMES
L2 TIMER T3: NOT IN USE			L2 WINDOW: 	7 FRAMES
L2 INTERFRAME FILL: 01111110		L2 LINE DOWN TIMER: 20 (NOT SUPPORTED)
  
LEVEL 3 PARAMETERS:

L3 USER DATA SIZE: 128 BYTES
L3 SEND WINDOW SIZE: 2 FRAMES
L3 MODULO: 8

L3 TIMER T20: 180 SECONDS
L3 TIMER T21: 200 SECONDS
L3 TIMER T22: 180 SECONDS
L3 TIMER T23: 180 SECONDS

L3 RESET RETRY COUNT : 5 TIMES 		L3 CLEAR RETRY COUNT: 5 TIMES
L3 FIRST PVC: 0 (=NOT IN USE)		L3 LAST PVE: 0 (=NOT IN USE)
L3 LIC: 0 (NOT SUPPORTED)		L3 HIC: 0 (NOT SUPPORTED)
L3 LTC: 1				L3 HTC:	16
L3 LOC: 0 (NOT SUPPORTED)		L3 HOC:	0 (NOT SUPPORTED)

USER FACILITIES:

NO USER FACILITIES

      *******************************************************

If you have time please also give me some advice, such as x25startup.ncl 
......osiapplication.dat.


Thanks in advance + best regards,


LK Lee
T.RTitleUserPersonal
Name		DateLines
869.1DELNI::MUGGERIDGEFri Feb 21 1997 05:2224
Why do you think the problem is profile related?

You need to provide some more evidence of this by tracing LAPB.

ctf
start lapb link *, display=(name),live, full

There is a list of profiles in our SPD.  You need to find one which
matches the characteristics of the NOKIA switch.  I suggest you
grab a copy of the SPD and issue the following command for each of
the profiles:

npl -r <PROFILE>

eg.  npl -r ISO8208

I don't have time to search for one for you.  However, keep in mind that
the default values don't have to be the same.  As long as the range of
vaues covers your requirements.  If the defaults don't match then you can
possibly modify the values via the configurator, or if necessary by editing
the file(s) /var/dna/scripts/*extra*

Good luck,
Matt.
869.2same problem ...HGOSPS::IVANCHENGThu Mar 13 1997 01:11214
    
    Hi, Matt
    
    
    We have also encountered the configuration problem between Digital UNIX
    and Nokia switch over x.25.  The network diagram is as follows :
    
    
    	+-------+			 +-------+
    	| OSF1  | DTE   +--+	DCE 	 | NOKIA |
    	|	|-------|ME|-------------| Switch|
    	+-------+       +--+		 +-------+
    
    
    
    The setting of the X.25 on the Nokia port is same as previous note
    (869.0).  We tried to use CCITT, ISO8208 and DATAPAK profile to test
    the communication but still unsuccessful.
    
    The LAPB link and L3 on the UNIX system could not sync. with the Nokia 
    switch.  For Detail, please see LAPB trace.  
    
    Do you has any suggestion ?
    
    THanks.
    
    Rgds,
    Ivan Cheng
    
    LAPB link setting on UNIX :
    
    ncl> show lapb link link-1 all
    
    Node 0 LAPB Link link-1
    AT 1997-03-12-19:20:03.215+08:00I-----
    
    Identifiers
    
        Name                              = link-1
    
    Status
    
        State                             = On
        Protocol State                    = Initialising
        Physical Port                     =
        Maximum PDU size                  = 1024
        Line Type                         = Nonswitched
        UID                               = 0D6B3D40-9ACA-11D0-8619-0000F821099B
    
    Characteristics
    
        Profile                           = "DATAPAK"
        Acknowledge Timer                 = 2000
        Sequence Modulus                  = 8
        Holdback Timer                    = 10
        Maximum Data Size                 = 1022
        Window Size                       = 7
        Interface Type                    = DTE
        Retry Maximum                     = 10
        Physical Line                     = Modem Connect Line line-1
        Poll Timer                        = 36
    
    Counters
    
        Times Link State Changed =                    5
        CRC Errors Received =                    0
        Data Octets Received =                    0
        Data Octets Sent =                   85
        Data PDUs Received =                    0
        Data PDUs Sent =                   17
        FRMRs Received =                    0
        FRMRs Sent =                    0
        Times Acknowledge Timer Expired =                  127
        Times PDU Transmit Failed =                    0
        Times PDU Receive Overrun =                    0
        REJs Received =                    0                    = 10
        Maximum Data Size                 = 1022
        Window Size                       = 7
        Interface Type                    = DTE
        Retry Maximum                     = 10
        Physical Line                     = Modem Connect Line line-1
        Poll Timer                        = 36
    
    Counters
    
        Times Link State Changed =                    5
        CRC Errors Received =                    0
        Data Octets Received =                    0
        Data Octets Sent =                   85
        Data PDUs Received =                    0
        Data PDUs Sent =                   17
        FRMRs Received =                    0
        FRMRs Sent =                    0
        Times Acknowledge Timer Expired =                  127
        Times PDU Transmit Failed =                    0
        Times PDU Receive Overrun =                    0
        REJs Received =                    0
       REJs Sent =                    0
        Polls Received =                    0
        RNRs Received =                    0
        RNRs Sent =                    0
        Times Link Halted =                    2
        Times Link Resetting =                   15
        Times Link Initialising =                    5
        Times Link Running =                    2
        Times Link Inoperative =                    0
        Times Link Maintenance =                    0
        Times Link Setup Failed =                    3
        Creation Time                     = 1997-03-12-19:16:19.295+08:00I-----
    
    ncl>
    
    
    
    LAPB trace : (using CCITT profile)
    ----------
    
    18:56:16.82|Disa|    0|link-1          | Link Disabled          |
    18:56:16.82|FLSH|    0|link-1          | Flush Issued to Driver |
    18:56:16.82|  Tx|    2|link-1          | C P DISC               |
    19:09:39.14|Enab|    0|link-1          | Link Enabled           |
    19:09:39.14|  Tx|    2|link-1          | C P DISC               |
    19:09:39.24|LNUP|    0|link-1          | Line Up                |
    19:09:45.18|AKTO|    0|link-1          | Ack Timer Expired      |
    19:09:45.18|FLSH|    0|link-1          | Flush Issued to Driver |
    19:09:45.18|  Tx|    2|link-1          | C P DISC               |
    18:56:16.82|Disa|    0|link-1          | Link Disabled          |
    18:56:16.82|FLSH|    0|link-1          | Flush Issued to Driver |
    18:56:16.82|  Tx|    2|link-1          | C P DISC               |
    19:09:39.14|Enab|    0|link-1          | Link Enabled           |
    19:09:39.14|  Tx|    2|link-1          | C P DISC               |
    19:09:39.24|LNUP|    0|link-1          | Line Up                |
    19:09:45.18|AKTO|    0|link-1          | Ack Timer Expired      |
    19:09:45.18|FLSH|    0|link-1          | Flush Issued to Driver |
    19:09:45.18|  Tx|    2|link-1          | C P DISC               |
    19:09:51.18|AKTO|    0|link-1          | Ack Timer Expired      |
    19:09:51.18|FLSH|    0|link-1          | Flush Issued to Driver |
    19:09:51.18|  Tx|    2|link-1          | C P DISC               |
    19:09:55.04|Rx  |    2|link-1          | R   DM                 |
    19:09:55.04|  Tx|    2|link-1          | C P SABM               |
    19:10:01.04|Rx  |    2|link-1          | R   DM                 |
    19:10:01.05|AKTO|    0|link-1          | Ack Timer Expired      |
    19:10:01.05|FLSH|    0|link-1          | Flush Issued to Driver |
    19:10:01.05|  Tx|    2|link-1          | C P SABM               |
    19:09:51.18|AKTO|    0|link-1          | Ack Timer Expired      |
    19:09:51.18|FLSH|    0|link-1          | Flush Issued to Driver |
    19:09:51.18|  Tx|    2|link-1          | C P DISC               |
    19:09:55.04|Rx  |    2|link-1          | R   DM                 |
    19:09:55.04|  Tx|    2|link-1          | C P SABM               |
    19:10:01.04|Rx  |    2|link-1          | R   DM                 |
    19:10:01.05|AKTO|    0|link-1          | Ack Timer Expired      |
    19:10:01.05|FLSH|    0|link-1          | Flush Issued to Driver |
    19:10:01.05|  Tx|    2|link-1          | C P SABM               |
    
    
    LAPB trace : (using DATAPAK)
    
    19:17:10.15|Disa|    0| Link Disabled          |
    19:17:10.15|FLSH|    0| Flush Issued to Driver |
    19:17:10.15|  Tx|    2| C P DISC               |
    19:17:18.76|Enab|    0| Link Enabled           |
    19:17:18.76|  Tx|    2| C P DISC               |
    19:17:18.86|LNUP|    0| Line Up                |
    19:17:20.77|AKTO|    0| Ack Timer Expired      |
    19:17:20.77|FLSH|    0| Flush Issued to Driver |
    19:17:20.77|  Tx|    2| C P DISC               |
    19:17:22.77|  Tx|    2| C P DISC               |
    19:17:22.77|AKTO|    0| Ack Timer Expired      |
    19:17:22.77|FLSH|    0| Flush Issued to Driver |
    19:17:22.77|  Tx|    2| C P DISC               |
    19:17:24.77|AKTO|    0| Ack Timer Expired      |
    19:17:10.15|Disa|    0| Link Disabled          |
    19:17:10.15|FLSH|    0| Flush Issued to Driver |
    19:17:10.15|  Tx|    2| C P DISC               |
    19:17:18.76|Enab|    0| Link Enabled           |
    19:17:18.76|  Tx|    2| C P DISC               |
    19:17:18.86|LNUP|    0| Line Up                |
    19:17:20.77|AKTO|    0| Ack Timer Expired      |
    19:17:20.77|FLSH|    0| Flush Issued to Driver |
    19:17:20.77|  Tx|    2| C P DISC               |
    19:17:22.77|  Tx|    2| C P DISC               |
    19:17:22.77|AKTO|    0| Ack Timer Expired      |
    19:17:22.77|FLSH|    0| Flush Issued to Driver |
    19:17:22.77|  Tx|    2| C P DISC               |
    19:17:24.77|AKTO|    0| Ack Timer Expired      |
    19:17:24.77|  Tx|    2| C P DISC               |
    19:17:25.04|Rx  |    2| C P SABM               |
    19:17:25.04|  Tx|    2| R F UA                 |
    19:17:25.04|  Tx|    7| C   I      0/0         |10 00 fb 00 00
    19:17:27.05|AKTO|    0| Ack Timer Expired      |
    19:17:27.05|  Tx|    2| C P RR     0/          |
    19:17:29.05|AKTO|    0| Ack Timer Expired      |
    19:17:29.05|  Tx|    2| C P RR     0/          |
    19:17:31.04|Rx  |    2| C P SABM               |
    19:17:31.04|FLSH|    0| Flush Issued to Driver |
    19:17:31.04|  Tx|    2| R F UA                 |
    19:17:31.04|  Tx|    7| C   I      0/0         |10 00 fb 00 00
    19:17:33.05|AKTO|    0| Ack Timer Expired      |
    19:17:33.05|  Tx|    2| C P RR     0/          |
    19:17:24.77|  Tx|    2| C P DISC               |
    19:17:25.04|Rx  |    2| C P SABM               |
    19:17:25.04|  Tx|    2| R F UA                 |
    19:17:25.04|  Tx|    7| C   I      0/0         |10 00 fb 00 00
    19:17:27.05|AKTO|    0| Ack Timer Expired      |
    19:17:27.05|  Tx|    2| C P RR     0/          |
    19:17:29.05|AKTO|    0| Ack Timer Expired      |
    19:17:29.05|  Tx|    2| C P RR     0/          |
    19:17:31.04|Rx  |    2| C P SABM               |
    19:17:31.04|FLSH|    0| Flush Issued to Driver |
    19:17:31.04|  Tx|    2| R F UA                 |
    19:17:31.04|  Tx|    7| C   I      0/0         |10 00 fb 00 00
    19:17:33.05|AKTO|    0| Ack Timer Expired      |
    19:17:33.05|  Tx|    2| C P RR     0/          |
869.3The Nokia is not receiving our framesOZROCK::MUGGERIDGEX.25 is 1-2-3Thu Mar 13 1997 16:2070
OK,

From your traces, it is not evident that your Nokia is receiving
anything.  Can you turn on the trace at the Nokia side too?

From the first trace, (CCITT profile), you can see that the UNIX box
is polling with DISC frames and the Nokia is polling with DMs.

The first time we see anything from the Nokia, it is a DM.  The UNIX box
responds to this with a SABM, but the Nokia apparently doesn't see this
because its next frame is a DM again.  Had the Nokia seen the SABM, its
response would have been a UA frame.

In your second trace, (DATAPAK profile), the UNIX box is once again polling
with DISC frames.  However, it seems you have modified the behaviour of
the Nokia, because now it is polling with SABM frames.

When the UNIX box first sees the SABM, it assumes the Nokia wants to
start the link, so we respond with a UA frame followed immediately by
an I-Frame from our client.  At this point, the UNIX box believes it
has a link in the running state!  However, once again, there is evidence
that the Nokia is not receiving packets, because it continues to poll
with the SABM frame, which resets the link.  From here it simply cycles
between running and resetting.

So in summary, the problem appears to be entirely on the Nokia side.
You will have to bang there door down to ensure they provide the support
you require.  At the very least, have them turn on trace to see why the
Nokia is not receiving any frames.

BTW, from the profiles you selected, you also need to take care with the
'L2 options'.  Both DATAPAK and CCITT do not support "Poll with SABM".
Once again, find out what L2 options the Nokia supports, and ensure they
match the profile you select for UNIX.

Here is the output from 'npl -r2 DATAPAK CCITT'.  Have a look at the
L2 Options to see what I'm referring to.


LAPB Profile : DATAPAK

Retransmit Timer : [    2000]      100 ->     3200
Max Data Size    : [     131]      131 ->     8196
Max Retransmits  : [      10]        2 ->       50
Max Window Size  : [       7]        7 ->        7

L2 Options
    DMs Supported        : No
    Poll with SABM       : No
    Poll with DISC       : Yes
    Poll with DM         : No
    SHUT state supported : No
    LAPB supported       : Yes
    LAPBE supported      : No
  
LAPB Profile : CCITT

Retransmit Timer : [    2000]      100 ->    10000
Max Data Size    : [    1028]      131 ->     8196
Max Retransmits  : [      20]        2 ->       50
Max Window Size  : [       7]        7 ->        7

L2 Options
    DMs Supported        : No
    Poll with SABM       : No
    Poll with DISC       : Yes
    Poll with DM         : No
    SHUT state supported : No
    LAPB supported       : Yes
    LAPBE supported      : No