"Bob’s Refunding E-Book V3" is an instructional manual for executing refund fraud against major retailers using tactics like FTID, empty box claims, and social engineering. The guide details methods to obtain free items or cash reversals, which carry significant risks of legal prosecution, permanent account bans, and potential exposure to malware. Learn more about the mechanics and risks of refund fraud at Bitsight .
Bobs_refunding_e-book_v3_all_addons_1_1 - (1).pdf
"Bob’s Refunding E-Book V3" is an instructional manual for executing refund fraud against major retailers using tactics like FTID, empty box claims, and social engineering. The guide details methods to obtain free items or cash reversals, which carry significant risks of legal prosecution, permanent account bans, and potential exposure to malware. Learn more about the mechanics and risks of refund fraud at Bitsight .
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.