While Status Quo is known for Boogie Rock , this track leaned more into Arena Rock and Pop Rock .
Its "You're in the army now" refrain has made it a staple in sports stadiums and military-themed media.
The title "Status Quo & Euro - In The Army Now (Remix)" likely refers to a contemporary EDM or Eurodance remix of the iconic 1986 hit by Status Quo. While various unofficial remixes circulate under "Euro" labels on platforms like YouTube and SoundCloud, the core of the track is based on one of the most successful covers in rock history.
В® Status Quo & Euro - In The Army Now (remix) В® Info
While Status Quo is known for Boogie Rock , this track leaned more into Arena Rock and Pop Rock .
Its "You're in the army now" refrain has made it a staple in sports stadiums and military-themed media. в® Status Quo & Euro - In The Army Now (Remix) в®
The title "Status Quo & Euro - In The Army Now (Remix)" likely refers to a contemporary EDM or Eurodance remix of the iconic 1986 hit by Status Quo. While various unofficial remixes circulate under "Euro" labels on platforms like YouTube and SoundCloud, the core of the track is based on one of the most successful covers in rock history. While Status Quo is known for Boogie Rock
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.