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

Conference smaug::snagwy

Title:SNA GATEWAY NOTEFILE
Notice:Note 1.* -> kits and doc, 288.* -> obtaining product support
Moderator:EDSCLU::GARROD
Created:Fri Feb 07 1986
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:7116
Total number of notes:28576

7116.0. "no response to NXID as in #7097" by BARNA::COLL () Thu Jun 05 1997 13:27

    	Hi everybody,
    
    	I am configuring an SNA Peer Server at a 
    customer site with the following elements:
    
    
      DUNIX ----- Token Ring--------3745 FEP ----IBM HOST.
    
    Host IBM requirements:
    DUNIX MAC address: 40-00-00-7c-09-00
    3745 MAC ADDRESS: 40-00-37-45-15-01
    DUNIX IDBLK=007
    DUNIX IDNUM=C0900
    
    This is a very similar scenario as reported in #7097, but
    in my case, the product versions are newer. 
    
    The installed Versions are:
    
    	Digital UNIX V4.0
    	SNA Peer Server V1.4
    	NCP: V7.3
    	VTAM: V3.4.2	
    
    The customer told me to change the MAC ADDRESS at the token
    ring interface to 40-00-00-7C-09-00. I did It in an extra 
    definition script when generating the ncl script with the
    t21config utility.
    
    
    
    After starting it, the local LLC2 starts sending and endless 
    series of NXID to its neighboring 3745, as it never gets any 
    answer from the 3745 counterpart.
    
    Here is how the llc2 sap link trace looks like:
    ctf> start llc2  sap sna-0 link link-0, live, full
    -----------+----+-----+<-----802.2 Frame Header------>+----
     Rem Time  |Evnt|Data |Dst Src C P Type    N     N    |DATA                    
    hh:mm:ss.ms|    |Size |SAP SAP R F        R/S   R/S   |                        
    -----------+----+-----+<----------------------------->+----
    16:40:10.50|  Tx|    3| 04  04 C P NXID               |
    16:40:13.50|  Tx|    3| 04  04 C P NXID               |
    16:40:16.50|  Tx|    3| 04  04 C P NXID               |
    16:40:19.50|  Tx|    3| 04  04 C P NXID               |
    16:40:22.51|  Tx|    3| 04  04 C P NXID               |
    16:40:25.51|  Tx|    3| 04  04 C P NXID               |
    16:40:28.51|  Tx|    3| 04  04 C P NXID               |
    16:40:31.52|  Tx|    3| 04  04 C P NXID               |
    16:40:34.52|  Tx|    3| 04  04 C P NXID               |
    16:40:37.52|  Tx|    3| 04  04 C P NXID               |
    
    
    As stated in 7097.1, I include 
    	A): The NCL startup script for the peer server, (mind
    	the mac address change at token ring interface)
    
    	B): The SWITCHED PU definitions.
    
    	C): I've got the NCP TIC definitions file, however, I
    	consider this is an unsuitable place to dump it due
    	to its large size.
    
    
    A) ----------------------NCL STARTUP SCRIPT:
    !
    ! Set up SNA Access Server Entity
    !
    create node 0 sna access server
    
    create node 0 sna access server object obj0 -
            transport = TCPIP, -
            port = 8001
    !
    ! Set up SNA Data Link Entity
    !
    !
    ! Set up LLC2 Entity
    !
    create node 0 llc2
    
    create node 0 llc2 sap SNA-0
    
    set node 0 llc2 sap SNA-0 -
            lan station = Token Ring station TRN-1, -
            local lsap address = 04
    
    create node 0 llc2 sap SNA-0 link LINK-0
    
    set node 0 llc2 sap SNA-0 link LINK-0 -
            acknowledge timer = 1000, -
            holdback timer = 500, -
            local receive window size = 127, -
            maximum data size = 2060, -
            remote lsap address = 04, -
            remote mac address = 40-00-37-45-15-01, -
            retry maximum = 10
    !
    ! Set up Token Ring Entity
    !
    create token ring
    
    create token ring station TRN-1 communication port tra0
    
    set token ring station TRN-1 ring speed 16
    !
    ! Set up SNA LU Services Entity
    !
    create node 0 sna lu services
    
    set node 0 sna lu services default transmission group = 
    !
    ! Set up SNA LU Services LU Entities
    !
    
    create node 0 sna lu services lu tr02 -
            dependent lu transmission group = tg-1, -
            dependent lu address = 2, -
            capability = Secondary, -
            old name = "sna-0.2"
    	.
    	.
    	.
    	many lu's defined... 
    	.
    	.
    	.
    
    create node 0 sna lu services lu tr81 -
            dependent lu transmission group = tg-1, -
            dependent lu address = 81, -
            capability = Secondary, -
            old name = "sna-0.81"
    !
    ! Set up SNA LU Services Access Name Entities
    !
    
    create node 0 sna lu services access name emulacion_3270 -
            lu list = {tr0*, tr1*, tr2*, tr3*, tr4*}
    
    create node 0 sna lu services access name impresoras -
            lu list = {tr5*, tr6*}
    !
    ! Set up SNA LU Services Authorization Entities
    !
    !
    ! Set up SNA LU Services Partner LU Entities
    !
    !
    ! Set up SNA CP Services Entities
    !
    create node 0 sna cp services -
            network id = VT3745, -
            cp name = icaro8, -
            maximum active TGs = 4
    
    create node 0 sna cp services transmission group tg-1 -
            data link = LLC2 sap SNA-0 link LINK-0, -
            intranode = No, -
            dependent lu support = Yes, -
            connection type = Permanent, -
            node id = %X007C0900
    !
    ! Enable all entities
    !
    !
    Start of optional file extra_definitions.ncl
    !
    !
    set token ring station trn-1 station address 40-00-00-7C-09-00
    !
    !
    ! End of optional file extra_definitions.ncl
    !
    enable node 0 llc2 -
        sap SNA-0
    enable node 0 llc2 -
        sap SNA-0 link *
    enable token ring station TRN-1
    enable node 0 sna lu services lu *
    enable node 0 sna cp services transmission group * 
    enable node 0 sna access server
    
    
    
    
    B)-------------SWITCHED PU DEFINITIONS:
    
    SWICARO  VBUILD MAXGRP=1,                                             
    +00001000
                   MAXNO=1,                                               
    +00002004
                   TYPE=SWNET                                              
    00003000
    *                                                                      
    00003200
    PUY000   PU    ADDR=01,IDBLK=007,IDNUM=C0900,MAXDATA=521,             
    *00003313
                   MAXPATH=1,VPACING=0,PUTYPE=2,SSCPFM=USSSCS,            
    *00003412
                   DLOGMOD=M32782,USSTAB=USSSNAR1,MODETAB=MODESA24         
    00003512
    Y000     LU    LOCADDR=002                                             
    00003813
    Y001     LU    LOCADDR=003                                             
    00003913
    Y002     LU    LOCADDR=4                                               
    00008101
    Y003     LU    LOCADDR=5                                               
    00008201
    Y004     LU    LOCADDR=6                                               
    00008301
    Y005     LU    LOCADDR=7                                               
    00008401
    Y006     LU    LOCADDR=8                                               
    00008501
    Y007     LU    LOCADDR=9                                               
    00008601
    Y008     LU    LOCADDR=10                                              
    00008701
    	.
    	.	
    	.
    	many lu definitions...
    	.
    	.
    	.
    Y01R     LU    LOCADDR=74,DLOGMOD=SCS                                  
    00039403
    Y01S     LU    LOCADDR=75,DLOGMOD=SCS                                  
    00039503
    Y01T     LU    LOCADDR=76,DLOGMOD=SCS                                  
    00039603
    Y01U     LU    LOCADDR=77,DLOGMOD=SCS                                  
    00039703
    Y01V     LU    LOCADDR=78,DLOGMOD=SCS                                  
    00039806
    Y01W     LU    LOCADDR=79,DLOGMOD=SCS                                  
    00039906
    Y01X     LU    LOCADDR=80,DLOGMOD=SCS                                  
    00040006
    *                                                                      
    00050000
    
T.RTitleUserPersonal
Name
DateLines
7116.1COPCLU::PALMANNFri Jun 06 1997 07:4913
Hi,
I had a problems like this some time ago.
If I where you, I would place an analyzer ( IRIS or som other ) at the same
ring as the 3745 FEP.
Then verify,
1. if the Peer servers NXID ever get's to the 3745 FEP's ring
2. if yes, does the 3745 FEP answers with an NXID 
   if no, verify ( with the analyzer ) that the 3745 FEP actualy uses address
   40-00-37-45-15-01
3. if the 3745 FEP, does the answer, find out why the answer does not get
   back to the Peer servers ring.

			Jan