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

Conference noted::dnu_osi

Title:DECnet/OSI for {ULTRIX,OSF/1}
Notice:Indicate version and platform when writing...see #2 for kits
Moderator:BULEAN::CARR
Created:Wed Sep 25 1991
Last Modified:Thu Jun 05 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2187
Total number of notes:10469

2146.0. "FTAM/OSI-LAN to ICL System 39" by MSAM03::RAHMAN () Mon Mar 17 1997 05:05

    
    Hi,
    I need help in setting up FTAM over OSI-LAN connection 
    between DIGITAL Unix 4.0x to ICL System 39 mainframe.
    
    Can anyone help me to configure the OSI-LAN and the osi 
    application (FTAM) setup. 
    
    I have been told by the ICL guys that I only need to 
    specify TSAP and MAC address to enable the connection 
    and FTAM.
    
    When i checked in the installation manual, we must use
    NSAP not the mac-address. (of course mac address is 
    part of NSAP). However we asked the ICL guys to also setup
    the NSAP. and when we try to do "oping" to the NSAP, 
    no response from the server. 
    Is there other way to trace the OSI-LAN connection other than oping?
    What should I configure on my Digital Unix?
    What should I supply to the ICL?
    What do I need from the ICL mainframe?
    
    I will be very happy if we can at least oping the mainframe.
    Although I heard that some older OSI-LAN version cannot
    support oping???
    
    Thank you in advance.
    
    Regards,
    rahman
    
T.RTitleUserPersonal
Name
DateLines
2146.1DRAGNS::RMULAC::S_WATTUMScott Wattum - FTAM/VT/OSAK EngineeringTue Mar 18 1997 11:3315
When ICL says "use the MAC address" they are probably refering to use of the
"inactive area subset" (I think that's what it's called now) - what I used to
call "Null Internet."  I can't remember the last time I've done this, but I
believe this is something you need to specify on the OSI Transport Template.
The DECnet-Plus documentation should have information on how to set this up.
Whatever the documentation has you specify as an address, will be what you also
want to use in the alias entry in the isoapplications file.

oping may or may not be a useful test here - ICL may not support it.

You might also try looking in HELP::OSI_APPL_SUPPORT and doing a title search on
the word ICL - sometimes people post what it took for them to set up the
connection to a particular machine.

--Scott
2146.2Setup Inactive AddressMSAM03::RAHMANFri Apr 04 1997 07:03120
    Thank you for the suggestion regarding the NULL Internet address on the
    OSI protocol.
    
    After some hard time, I have managed to establish FTAM operation via
    the
    "inactive address area" to ICL 39.
    
    Here is my step:
    
    1. Install the Decnet/OSI as usual.
       eg. setld -l .  ( in the dna400 on the SPL cdrom)
       
       reinstall:
       # decnetsetup basic
    
    2. After installation check if any routing circuit is setup.
    
      # ncl <CR>
        ncl> show routing circuit * state
        eg.
    
    Node 0 Routing Circuit circuit-1
    AT 1997-03-21-15:24:31.907+08:00I-----
    
    Status
    
        State                             = On
    
    3. CHange the status of the all circuit to Off.
    
        ncl> disable routing circuit *
        ncl> show routing circuit * state
    Node 0 Routing Circuit circuit-1
    AT 1997-03-21-15:24:31.907+08:00I-----
    
    Status
    
        State                             = Off
    
    4. Create new routing circuit for the "inactive address area" with type
    of
    csma-cd.
    
        ncl> create routing circuit csmacd-0 type csma-cd
        ncl> set routing circuit csmacd-0 inactive area address {49::00-FF}
    
    5. Check for the Data Link Entity from the existing circuit.
    
        ncl> show routing circuit * data link entity
    
        eg.
    Node 0 Routing Circuit circuit-1
    AT 1997-03-21-15:31:05.800+08:00I-----
    
    Characteristics
    
        Data Link Entity                  = CSMA-CD Station csmacd-1
    
    
    
    6. Attach Data Link Entity as found in 5) to the new circuit just
    created 
       in 4) above.
    
      ncl> set routing circuit csmacd-0 data link entity CSMA-CD station
    csmacd-1
    
    
    7. Enable the routing circuit.
    
      ncl> enable routing circuit csmacd-0
    
    8. Edit the /etc/isoapplications  file to match the "inactive address"
    as
    specified in 4) with the following parameters:
       SSAP= <empty>
       PSAP= <empty>
       TSAP= %XXXX  where XXXX is correspondingly for the local and remote
    system.
       NSAP= <Inactive address area>:MAC address:21
    
    eg in the /etc/isoapplications
    
    
    my_host   :FTAM:::..%x0001. \
               %X4900FF0000F831136721, \
               provider=osi,template=default:
    
    remotehost:FTAM:::..$2882. \
               %X4900FF08000D000A4721, \
               provider=osi, template=default:
    
    9. Kill all existing FTAM and VT listener
        # ps -ef |grep listener
          PID1   ftam_listener
          PID2   vt_listener
        # kill -9 PID1 PID2
    
    10. Restart listener using new "inactive address" alias as specified in
    /etc/isoapplications.
    
       # ftam_listener my_host
    
    11. Test ftam to your own host.
        # ocp my_host/root/rootpasswd::/etc/motd /tmp/newmotd
        verify the file is copied.
    
    12. Test ftam across the system.
    
        # ocp remotehost/USER1/PASS1::TESTFILE /tmp/rtestfile
        verify the file is copied.
    
    13. To enable the trace, set OSAK_TRACE=ON
    
        # OSAK_TRACE=ON export OSAK_TRACE
        and retry the ocp.
    
    14.  Good luck.
    
    rahman
2146.3It shouldn't have been that hardDRAGNS::RMULAC::S_WATTUMScott Wattum - FTAM/VT/OSAK EngineeringFri Apr 04 1997 12:057
Really, I think all you had to do was set the CLNS inactive area address on a
particular osi transport template and then specify that template in the
isoapplication file.  Possibly you might have had to create another routing
circuit asd well, but I don't recall inactive areas ever being as hard to setup
as what you just described.

--Scott
2146.4alphy.lkg.dec.com::thomasThe Code WarriorFri Apr 04 1997 12:102
No reason to create another circuit.  Just set the inactive area
prefix on the csmad circuit.
2146.5Thanks Scott...MSAM03::RAHMANThu Apr 10 1997 03:005
    Yes, i did not explore on that option. But the customer was on my back
    and i found an old decnet/osi explains about creating another circuit.
    And it works.
    
    Thanks guys.