|
|
|
|
|
|
|
|
|
|
|
| SYMPTOM:: Loss of aft transfer functionality repeatedly refuses connection to the SST. | ||||||||||
| BACK | ||||||||||
| May affect OCC, AMA or both. | ||||||||||
| CAUSE:: Due to processor loading, only 3 simultaneous connections are allowed for the AFT function. The DAIS or Data access information service is the controller that RASL uses to route the files from DIRP to AFT. This is the entity allowing only 3 connections. When the connection to the server or the physical path to dirphold is torn down, the virtual connections or sessions become hung. In our case 2 of the 3 sessions were hung allowing us 1 additional connection; this being either AMA or OCC but not both. | ||||||||||
| SOLUTION:: Nortel reports this has only occurred 13-14 times in the past 2 years and in all cases a warm restart in the form of a maintenance swact was required to clear the problem. | ||||||||||
| ALARMS AND LOGS:: AFT alarms are generated as normal but log AFT002 is output. | ||||||||||
| NAILING IT DOWN:: the OMSHOW DAISGEN counter pegs are about the only way to truly confirm it is a problem with the DAIS connections. These counters are pegged for creation and teardown of a DAIS connection. The errors will never increment if they are hung connections. | ||||||||||
| NOTES:: Tear down both connections in tables raslappl and gasinfo. Then rebuild them and see if they both connect. If only 1 connects then wait 15 minutes and then delete the tuple for the working connection in table raslappl, if when this connection is deleted the other begins working then you have the same problem as we do. Ensure that the OM logs are enabled for DAISGEN. | ||||||||||