ITEM: BL7252L
sna link station doesn't start
SNA Link Station Error Messages Descriptions.
These are common Link station error messages when trying to start a link
station for SNA Server/6000 and IBM Communications Server.
ERROR: 0105-2905 The Link Has Experienced an Unusual Physical
Network Condition Error:
DESCRIPTION: AIXSNA made a call to the DLC trying to do an open, but the
open of the sap/port for the token ring failed because it could not
access that port due to a physical problem. Additional information
is below:
If this is SDLC---
1.) Check the state of the link station. See if it is starting and
what the lights look like. More than likely it will be
impossible to get a trace and the modem lights will not
look normal.
2.) The physical setup is a very common cause for this error. A bad
SDLC adaper, cable, or breakout box, along with a incorrectly
configured modem can cause these problems.
3.) The modem config and setup along with the VTAM line definition
needs to match up with SNA DLC profile. You need to make sure
that the network type (switched/nonswitched), NRZI/NRZ, and that
the bit clocking is EXTERNAL.
4.) Make sure that the customer is pointing to correct port that the
cable is plugged into and that that port is available.
'lsdev -Cc port' will show which ports are available and the
port is known to sna from the 'Data link device name' field in
the SNA DLC profile.
If this is Token Ring---
1.) Make sure that the token ring is set for the correct ring speed.
Whether it be 4M or 16M.
2.) It could possibly be a hardware problem. Check the system error
log for errors, check the cable, and run diag on the adapter.
3.) Make sure that there is not duplicate CP names on this SNA
network!!!
LINK TRACE: Link tracing will not be possible. DLC tracing might be
possible, but not a sure thing.
__________________________________________________________________________
ERROR: 0105-2920 Link Station Cannot Find Specified Remote.
DESCRIPTION: The AIXSNA DLC is sending out test frames that are not getting
responded back too. Some of the reasons for this are below:
1.) Incorrect remote link address in the link station profile
2.) If ethernet you might need to use the bit reversed address.
3.) Check the network setup for routers or bridges that might be
causing problems. (need source route bridging)
4.) 3174s need to be coded to have a subaddress of the RS/6000s
adapter address.
** For test frames being sent out over a complex network (through routers
and/or bridges, etc..) then the RS/6000 will send out a single route
TEST frame. If the first few test frames are not answered then the
AIXSNA DLC will now send out a broadcast explorer TEST frame, this is
seen by looking at the first bit in the address it is looking for being
reversed.
LINK TRACE: Link tracing is possible, but must be turned on before the
attempt to start the link station either from smit, the command
line, or from within the link station profile.
____________________________________________________________________________
ERROR: 0105-2916 Link Station Terminated Due To Line Inactivity.
DESCRIPTION: For SDLC this error means that we probably tried to raise DTR
on the modem, but the two modems did not sync up for some reason.
For LAN based the AIXSNA DLC and Server is sending out NULL XIDs,
but they are not getting a response back to those XIDs.
More information is below:
If this is SDLC---
1.) Check the state of the link station. See if it is starting and
what the lights look like.
2.) One common cause is that they have the wrong
"Local Secondary Station Address"
in the link station profile.
This is from the ADDR field in the PU definition and needs to
be converted to decimal in the link station profile.
If this is LAN based---
1.) This is often caused by the PU (VTAM) or controller (AS/400) not
being in the correct state when we try to contact them. If the
PU is inactive or the controller is Varied OFF, then the above
error could result.
2.) This error can also come about from the RS/6000 pointing to an
incorrect PU. For instance if we are going through a 3745 and
we are not pointing to the correct XID (IDBLK+IDNUM from switched
major node PU defintions), we could get this error. If we are
going through a 3174 and the 3174 is not configured to point to
the correct PU then the error could also occur.
3.) If they have CPNAME coded in under the PU in the switched major
node definitions then the CP name in the control point profile
on the RS/6000 must match that field exactly. Also make sure that
the NETID from VTAM matches the Network Name in the control point
profile.
4.) Make sure that they are pointing to the correct 'Remote SAP Address'
in the link station profile. This usually needs to be 04 as
0x04 is reserved for SNA type trafficing.
If this is channel---
1.) This is normal return from the attempt to start a channel attached
link station. This means that RS/6000 is now waiting for the
PU to go active. So at this point they should try to bring the
PU all the way active.
LINK TRACE: Link tracing is possible, but must be turned on before the
attempt to start the link station either from smit, the command
line, or from within the link station profile. If this is SDLC,
there will not be a trace created unless the RS/6000 receives
frames coming in over the SDLC Communications adapter.
____________________________________________________________________________
ERROR: 0105-2725 Link Station Has Become Inactive
DESCRIPTION: This error usually occurs due to a failure in the XID(3)
negotiations with the remote node. Look below for more information:
PUTYPE 2.1---
1.) Check and make sure that we are going to the correct PU/Controller
by checking the XID values, or the 3174 config, or the AS/400
controller, network attributes and line definitions.
2.) Make sure that we are not using the same CP name as another node
on the SNA network.
3.) If going to an AS/400 turn Solicit SSCP sessions off in the link
station profile.
4.) The best thing to do is look at a link station trace and check out
the flow of the network names and CP names from node to node.
Look at the detailed trace for the field name of--
'Exchange states indicator'
This field with a send XID(3) will start as 'Pre-negotiation',
After a few XID(3) exchanges this field should change to
'Negotiation proceeding'. If this change does not take place
on BOTH the send and receive XID(3)'s, the link station will
time out and exhaust the poll count for XID negotiations.
The best thing to do in this circumstance is to have them
recycle the PU (VTAM) or the Controller (AS/400).
NOTE: SDLC will not normally do XID negotations.
LINK TRACE: Link tracing is possible, but must be turned on before the
attempt to start the link station either from smit, the command
line, or from within the link station profile.
The information contained in this item was put here to help with
contextual searches about link station errors when trying to
start the link station.
Support Line: sna link station doesn't start ITEM: BL7252L
Dated: March 1997 Category: N/A
This HTML file was generated 99/06/24~13:30:21
Comments or suggestions?
Contact us