Hi Everyone!
First off, I want to say that the subnet management forum posts are a fantastic idea—they really help make the voting process much more transparent. As we’re going through this for the first time, I also want to acknowledge that, as a Node Provider (NP), I wasn’t initially aware of the importance of communicating certain updates through the forum. Up until now, we’ve been relying mainly on the Matrix channel for maintenance updates. As per my matrix post in July
as shown here : Subnet Management - tdb26 (NNS) - #10 by MalithHatananchchige
I realize now that this wasn’t the best approach, and I’ll be updating the Wiki with this information to help future NPs avoid the same oversight.
For example, here are two Wiki pages that I plan to update with my learnings:
The main reasons an NP might request to remove a node from a subnet usually involve:
- Hardware failure
- Network device failure
- IP and connectivity issues, including migration
In my case, the proposals to migrate the CM1 nodes from an issue where our ISP assigned IP addresses that are not recognized as local, even though latency remains unchanged. To resolve this, we’ve taken steps to obtain our own local IPv4 and IPv6 subnets.
As you can see in the screenshot @Lorimer posted,
the CM1 IP addresses are currently geolocated in India. This presents a challenge for us in proving that we are indeed operating out of Colombo, Sri Lanka. To address this, we decided to purchase a local IP subnet, as we anticipate audits from Dfinity in the near future. This migration will not only correct the geolocation data in the GeoDB but also provide us with access to a larger IPv4 subnet, which will be beneficial as the Internet Computer (IC) begins encouraging NPs to incorporate IPv4 in their node clusters.
I hope this migration makes sense, and once again, I sincerely apologize for not communicating this on the forum earlier and only using the Matrix channel. I appreciate your understanding—it’s my first time handling ongoing maintenance as an NP, and I’m learning as I go.
Thank you for your support and patience!