Switch NSP Telegram appears to be a channel or group on the messaging platform Telegram, focused on sharing and discussing information related to the Nintendo Switch console, specifically Non-Standard Products (NSP) or homebrew content.
No, Switch NSP Telegram appears to be an unofficial community-driven channel, not affiliated with Nintendo or its official developers. The content shared on this channel may not be officially supported or endorsed by Nintendo.
NSP files are a type of file format used by the Nintendo Switch console to distribute and install games and other content. NSP files can contain game data, updates, or other types of content, and are typically used for homebrew or custom content that is not officially supported by Nintendo.
Switch — Nsp Telegram
Switch NSP Telegram appears to be a channel or group on the messaging platform Telegram, focused on sharing and discussing information related to the Nintendo Switch console, specifically Non-Standard Products (NSP) or homebrew content.
No, Switch NSP Telegram appears to be an unofficial community-driven channel, not affiliated with Nintendo or its official developers. The content shared on this channel may not be officially supported or endorsed by Nintendo. switch nsp telegram
NSP files are a type of file format used by the Nintendo Switch console to distribute and install games and other content. NSP files can contain game data, updates, or other types of content, and are typically used for homebrew or custom content that is not officially supported by Nintendo. Switch NSP Telegram appears to be a channel
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.