"Take Control of Your Internet Experience with My Account Ticfiber"
Are you a Ticfiber customer looking for a seamless and convenient way to manage your internet account? Look no further than My Account Ticfiber! With this user-friendly online portal, you can effortlessly monitor and control your internet usage, pay bills, and access a range of exciting features. In this post, we'll dive into the benefits and features of My Account Ticfiber and show you how to make the most of this powerful tool.
Myaccount.ticfiber.in -
"Take Control of Your Internet Experience with My Account Ticfiber"
Are you a Ticfiber customer looking for a seamless and convenient way to manage your internet account? Look no further than My Account Ticfiber! With this user-friendly online portal, you can effortlessly monitor and control your internet usage, pay bills, and access a range of exciting features. In this post, we'll dive into the benefits and features of My Account Ticfiber and show you how to make the most of this powerful tool. myaccount.ticfiber.in
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.