QUESTION:
I'm in the process of setting up a sna/hcon session on a
Token Ring attached RS/6000 to a 3090 host that is Token Ring attached
via a 3745 tic. I'm using item #3VPCM -- HOWTO AIX: Steps necessary
to configure sna services and hcon to communicate vi token-ring in
aix 3.2. My RS/6000 is a 58f with aix 3.2.5.
I have several questions regarding the configuration process:
1. In section "Configure the T/R Physical Link Profile:
a. Could you define to a laymen what the Local SAP address is
and where it comes from?
2. In section " Add SNA Control Point Profile":
a. In the howto it states that the xid node id is the concatenation
of the IDBLK and IDNUM. In this example the IDBLK is 071. Is
there any significance to the number. My customer mentioned that
usually 017 is used for a 3174(I think). Is this correct? Is
071 represent an rs/6000 perhaps?
3. In section "Configure the T/R Physical Link Attachment Profile":
a. Why is Call type toggle to call?
b. The howto states that the Remote Link address is the address of the
LAA of the TIC you are connecting to. If this is the case where
does the address the RS/6000 come into play. In my example the
LAA of the TIC is 400001220000. The address of the RS/6000 should
be 400070130036. Where do I use this second number?
c. What is the Remote SAP address and where do I obtain this value?
How does it relate to the Local SAP address found in the T/R
physical link profile?
4. In the section of "verify your physical configuration":
a. When I issue "startsrc -t attachment -o TOKEN" it appears
to insert on the ring but after a minute or so the system
responds with the following message:
0513-056 Timeout waiting for command response
Does this message occur because I don't have my values in VTAM yet?
The VTAM configuration should be done by Monday.
5. In section "Configure the Local Logical Unit Profile":
a. Is the SSCP ID the subarea address in Hex added to 05000000001?
In my case the subarea address for my production vtam is 01 so
what should I use as a valid SSCP ID?
b. How many of these LU2 Local LU profiles do I need? I notice in
the sample vtam listing there are 7 Local LU addresses defined.
In our case there will be 32 (002 to 033). Do I need to create
profiles for all of these?
6. In section "Configure the Local Logical Connection Profile":
a. Do I need to configure profiles for each of the REMOTE LU names
I have defined in VTAM?
b. Can you give me a laymen definition of REMOTE LU name?
Sorry for the long list of questions. I would really like to
understand this configuration process so in the future I'll understand
more of what I'm doing instead of just following the instructions
---------- ---------- ---------- --------- ---------- ----------
A: I will respond to your questions in the order they were asked,
and then will point you to some helpful documentation on SNA
Services/6000.
1. Service Access Point (SAP): This is a numeric value used to
uniquely identify an application that can co-exist at a given
network address with other applications. Applications local
to a node can create a SAP with a particular value, and
applications on remote nodes can send data or establish
a connection to a SAP of a particular value at a local node.
An example of a special SAP value is 0x04, used by SNA.
Another, 0xAA, is used by Sub-Network Access Protocol (SNAP)
to convert Standard Ethernet packets to IEEE 802.3 format.
Local SAP address is SAP address for the transaction program
on the local system. It does not have to be unique
within the network. If you are setting up a new network,
assign a value of 04 as the SAP address for each SNA
Services/6000 node in the network.
2. Yes this number is significant and should be the same
on RISC and host.
Yes, code 071 conventionally represents RISC/6000,
however, RISC also can be represented by any other number as
long as both entries are consistent on the host and RISC.
Yes, 017 stands for 3174.
3.
a. "Why is Call type toggle to call?"
CALL type field indicates whether a local station
initiates a connection or receives requests for a
connection from another station. The following values are
valid in this field:
CALL : Select this value to indicate that the
local station initiates the attachment by calling
another station. If you select this option, you can
request the access routing.
LISTEN : Select this value to indicate that the
local station does not initiate an attachment, but waits
for a remote station to make an attachment with it.
b. RISC's address should be set up in the VTAM in order for host
to be able to establish connection. I assume that it was LAA and
was given to you by network administrator. In this case you also
have to set this value in the field "Enable ALTERNATE TOKEN RING
address" while changing configuration of your Token Ring adapter.
It can be performed with the command:
'smit chgtok'
c. Remote SAP address. This value should be changed
only if the ACCESS ROUTING field is link_address. The
Remote SAP address field specifies the SAP address for the
remote system. This address is hexadecimal value, in
multiples of two, in the indicated range. The value
entered must be the same as the value defined for the
local SAP address field of physical link on remote station.
It does not need to be unique within the network. If you are
setting up a new network, assign a value of 04 as the
Remote SAP address for each SNA Services/6000 node in the
network.
4.The error message looks like an address error. Most
likely, it occurs because values in VTAM are not set up
yet and it can not install connection with RISC (see answer
to question 3, part b).
5. a. No, the SSCP ID is subarea address added to 05000000000.
If your subarea address is 01 then added to 05000000000, it
will result 05000000001, which will be your SSCP ID.
b. You need to create one Local LU profile for each
dependent HCON session.
6. a. Yes, you have to configure profiles for each
REMOTE LU name defined in VTAM.
b. REMOTE LU name is a name assigned to LU as it is
described in VTAM.
To get more detailed information on the issue of configuring
SNA sessions you might want to refer to the following
documentation:
* "AIX SNA Services/6000 Reference" (SC31-7014-00).
* "AIX SNA Services/6000 Profile Configuration" (GG22-9493-00).
---------- ---------- ---------- --------- ---------- ----------
This item was created from library item Q655737 CQKTN
Additional search words:
ATTACHED COMMUNICATIO CQKTN HCON IX MAR94 OZNEW QUESTION RISCSNA
RISCSYSTEM SETUP SNA SOFTWARE 3745
WWQA: ITEM: RTA000040631 ITEM: RTA000040631
Dated: 11/1996 Category: RISCSNA
This HTML file was generated 99/06/24~12:43:16
Comments or suggestions?
Contact us