Last Modified: Nov 07, 2022
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9
Opened: May 29, 2013 Severity: 3-Major Related Article:
Related Article: K14725
Some connections through the CGNAT may not have corresponding LSN logs associating those translation address-port end-points with an FTP subscriber. This only occurs on an LSN with NAPT mode with an FTP-ALG profile, and it only occurs for a subscriber using FTP Active mode.
There are CGNAT sessions missing from the LSN logs.
LSN with NAPT mode FTP-ALG profile Subscriber using FTP Active mode
Associate the subscriber with the FTP control channel. Provide both the control channel and data channel end-points so the subscriber can be correctly located.
Data connections created through FTP Active-mode transactions through the CGNAT now have the data session translation address:port logged as LSN translations.
ALG now has an option enabled with a db var to log the messages and media/data connections so that they can be traced to an LSN subscriber.