Critical fixes for vulnerabilities that targeted the PDF engine, which was a high priority during the early 2010s.
Released around May 2013, version 11.0.03 was a significant planned update for the Acrobat XI series. It introduced several security enhancements and functional improvements over the base version of Acrobat XI Pro.
It was the only version to bundle FormsCentral , a standalone tool for creating both PDF and web forms with built-in data collection.
^hot^ | Adobe Acrobat Xi Pro 1103 Multilanguage Chingliu Updated
Critical fixes for vulnerabilities that targeted the PDF engine, which was a high priority during the early 2010s.
Released around May 2013, version 11.0.03 was a significant planned update for the Acrobat XI series. It introduced several security enhancements and functional improvements over the base version of Acrobat XI Pro. adobe acrobat xi pro 1103 multilanguage chingliu updated
It was the only version to bundle FormsCentral , a standalone tool for creating both PDF and web forms with built-in data collection. Critical fixes for vulnerabilities that targeted the PDF
This could have to do with the pathing policy as well. The default SATP rule is likely going to be using MRU (most recently used) pathing policy for new devices, which only uses one of the available paths. Ideally they would be using Round Robin, which has an IOPs limit setting. That setting is 1000 by default I believe (would need to double check that), meaning that it sends 1000 IOPs down path 1, then 1000 IOPs down path 2, etc. That’s why the pathing policy could be at play.
To your question, having one path down is causing this logging to occur. Yes, it’s total possible if that path that went down is using MRU or RR with an IOPs limit of 1000, that when it goes down you’ll hit that 16 second HB timeout before nmp switches over to the next path.