Getting Started with Linux-SNA

Quick configuration of your Linux-SNA server

 

Copyright:
Copyright 2001 (c), All rights reserved. Jay Schulist <jschlst@samba.org>


Written by:

Jay Schulist <jschlst@samba.org>

This is the third Linux-SNA Getting Started Guide in the series. This guide will assist you in the configuration process of a Linux-SNA server. This guide assumes the user does not know much about SNA, but a user that knows nothing about SNA will have a difficult time. Do not be discouraged if your Linux-SNA server does not work right away, please follow the instructions as close as possible and then if you have problems contact the Linux-SNA mailing list linux-sna@turbolinux.com (archives and list info at http://www.turbolinux.com/mailman/listinfo/linux-sna) where someone or myself will be happy to help you solve your problem.

Snachers!


1. Read the Quick installation of your Linux-SNA server guide to get a Linux-SNA server installed and all the software in the correct places.

2. If at all possible please verify your installation using the guide Verify correct installation of your Linux-SNA server before proceeding to step 3.

3. Please remember:

4. What is Snaconfig?

5. Information required to setup a Linux-SNA server. Please use the following work-sheet to obtain all the necessary information then proceed to step 6. If you are not sure of what data is needed you may be able to click the name of the requested data (The name on the left side of the table) which will provide you with additional information. Not all information may be required, but if you can obtain it, all the better. You may need to define multiple Local and Remote LUs, Cost-Of-Service definitions, Modes or CPI-C Side information. Simply repeat entering the data on the same form or print out another for to use for the additional definitions.

Step

Data Requested

Data Required 
1 - Global Node Parameters  

1
Fully Qualified CP Name  

2
Node Type  

3
Node ID  
     
2 - Datalink and Port Parameters  

1
Local network device name  

2
Local port  

3
Role  

BTU Size  

5
Maximum Outbound Activations  

6
Maximum Inbound Activations  
     
3 - Link Parameters  

1
Link interface  

2
Port  

3
Byteswap  

4
Destination MAC address  

5
Destination port  

6
Partner LU name  

7
Retry on failure  

8
Number of retries  

9
Autoactivation  

10
Autodeactivation  

11
Transmission group number  

12
Cost per byte  

13
Cost per connect  

14
Effective capacity  

15
Propagation delay  

16
Security  

17
User 1  

18
User 2  

19
User 3  
     
4 - Local LU Parameters  

1
Name  

2
Syncpoint support  

3
Session limit  
     
5 - Remote LU Parameters  

1
Partner LU name  

2
Fully Qualified CP Name of Partner  
     
6 - Cost of Service Parameters  

1
Name  

2
Weight  

3
Transmit Priority  

4
Default COS if invalid  

5
Default COS if null  

6
Minimum Cost Per Connect  

7
Maximum Cost Per Connect  

8
Minimum Cost Per Byte  

9
Maximum Cost Per Byte  

10
Minimum Security  

11
Maximum Security  

12
Minimum Propagation Delay  

13
Maximum Propagation Delay  

14
Minimum Effective Capacity  

15
Maximum Effective Capacity  

16
Minimum User 1  

17
Maximum User 1  

18
Minimum User 2  

19
Maximum User 2  

20
Minimum User 3  

21
Maximum User 3  

22
Minimum Route Resitance  

23
Maximum Route Resitance  

24
Minimum Node Congestion  

25
Maximum Node Congestion  
     
7 - Mode Parameters  

1
Name  

2
COS Name  

3
Partner LU Name  

4
Encryption  

5
Transmit Pacing  

6
Receive Pacing  

7
Maximum Transmit RU  

8
Maximum Receive RU  

9
Minimum Contenetion Winners  

10
Maximum Contention Winners  

11
Max Sessions  

12
Autoactivation  
     
8 - CPI-C Side Information  

1
Symbolic Destination Name  

2
Mode Name  

3
Parnter LU Name  

4
Transaction Program Name  

6.