Guest

Preview Tool

Cisco Bug: CSCtb92685 - SNASw: LOCATE-FOUND-NOTIFY (12CC) rejected with 1014003C (VTAM FFST)

Last Modified

Nov 18, 2014

Products (1)

  • Cisco IOS

Known Affected Releases

12.4(13d)

Description (partial)

Symptom:
LOCATE-FOUND-NOTIFY (12CC) rejected by VTAM with SNA SENSE DATA 1014003C.  May
result in an FFST probe dump on VTAM.   This is in response to a
LOCATE-FIND-NOTIFY from VTAM NNS.

Conditions:
Here is the customer's configuration:   
                                         
     vleb <-> vlea <-> ilesna11 <-> dependent LU
 
       en           nn       en
 
      adaimc    dlus     dlur             
 
 
 - net02.vleb is an EN
 - net02.vlea is a NN/DLUS
 - net02.ilesna11 is a Cisco SNASw router, DLUR for downstream PU type 2
cluster controllers servicing LU2 videos and LU1 printers
 
 - typically the first LU within a PU has a LOGAPPL=ADAIMC (it's a special LU
type 1 session that the customer calls a command handler that doesn't support
user sessions) 
 - ADAIMC is one of the customer's IMS applications
 
                                   
   At the time that the autologon was initiated the appl  adaimc had not yet
done OPEN ACB, so was in a CONCT state to vtam.
 
  When adaimc opened its ACB, vtam would send out a LOCATE FOUND NOTIFY  with a
"resource enabled" indicator set in the NOTIFY (12CC gds). 
 
  The problem is that when it is sent to ILESNA11, it's returned to  VLEA with
incorrect configuration info.  There are two vector 3C's and one vector 3D
(that's ok) but the first 3C indicates the NN is ILESNA11,   the second 3C
indicates EN is ILESNA11, and the 3D indicates the LU is  ILESNA11. Since
ILESNA11 is a CISCO box, we believe it should reject the 12CC with a sense code
(10105002?) instead of replying as it did.  Note that the LOCATE FOUND NOTIFY
did not have the owning CP respond bit turned  on. If the LOCATE FOUND NOTIFY
had been rejected, the session should have been set up as VTAM would do a
broadcast to do the notification.
 
 Further Problem Description:

 The LOCATE-FOUND-NOTIFY with the incorrect vector topology from the SNASw
caused a VTAM FFST probe dump, and stopped further processing on the session
reallocation.  Had the FFST probe not been issued by VTAM, the
LOCATE-FIND-NOTIFY would have reached the subarea side of VTAM, and the LOGAPPL
session would have been reallocated.
 
 Here is the LOCATE FOUND NOTIFY reply received from the Cisco box,
 showing the two x'3C' vectors and the x'3D' vector: 
 
 10:32:37.235 D7C9E440 3F990004 0FC5D520 40000000 00000000 00000001 00010001
1C000007 *PIU .r...EN. ...................* 
 10:32:37.235 D7C9E4F2 023D0573 00C50B91 81300502 FF0003D0 00000422 F0F0F300
170ED5C5 *PIU2.....E.ja...... ....003...NE* 
 10:32:37.235 D7C9E4F2 E3F0F24B C9D3C5E2 D5C1F1F1 C3D9E9C7 C4380001 083E2B00
76659284 *PIU2T02.ILESNA11CRZGD.........kd* 
 10:32:37.235 D7C9E4F2 00002412 C4400000 10121560 DA47C377 B30119A1 0AD5C5E3
F0F24BE5 *PIU2....D .....-..C.... .NET02.V* 
 10:32:37.235 D7C9E4F2 D3C5C206 81000001 12003E12 CB048080 01123C00  F6D5C5E3
F0F24BC9 *PIU2LEB.a...............6NET02.I* 
 10:32:37.235 D7C9E4F2 D3C5E2D5 C1F1F112 3C00F4D5 C5E3F0F2 4BC9D3C5  E2D5C1F1
F1123D00 *PIU2LESNA11...4NET02.ILESNA11...* 
 10:32:37.235 D7C9E4F2 F3D5C5E3 F0F24BC9 D3C5E2D5 C1F1F100 3012CC02  00002919
00000008 *PIU23NET02.ILESNA11.............* 
 10:32:37.235 D7C9E4F2 D5C5E3F0 F2404040 08C1C4C1 C9D4C340 4008D5C5 E3F0F240
404008C1 *PIU2NET02   .ADAIMC  .NET02   .A* 
 10:32:37.235 D7C9E4F2 C4C1C9D4 C3404000 00000000 00000000 00000000 00000000
00000000 *PIU2DAIMC  .....................*
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.