chore: cleanup STRYKAR AS4242422174

[yzguy]

Related #62 #95 #102

Cleanup STRYKAR AS4242422174 in MUM1 due to inactivity and non functioning peering configuration

TASK [dn42 : wireguard | resolve IPv6 address for STRYKAR-MUM] *****************
fatal: [router.mum1]: FAILED! => 
  msg: 'An unhandled exception occurred while running the lookup plugin ''community.general.dig''. Error was a <class ''ansible.errors.AnsibleError''>, original message: dns.resolver unhandled exception All nameservers failed to answer the query mum1.dn42.4v1.in. IN AAAA: Server Do53:10.96.0.10@53 answered SERVFAIL. dns.resolver unhandled exception All nameservers failed to answer the query mum1.dn42.4v1.in. IN AAAA: Server Do53:10.96.0.10@53 answered SERVFAIL'

DNS record provided does not resolve to anything, and BGP session has never come up since addition

We have no peers in MUM1/MAA1 so we will likely decomm these nodes soon

[github-actions]

Hello,

We have started the deployment of new configuration on our side for the peering at our MUM1 PoP.
It is ready for the configuration on your side.

You can use our Nodes page for PoP information to be used: https://dn42.routedbits.com/nodes/#mum1

We manage configuration via our dn42-peers repository, you can submit pull requests to add/remove/change your own peerings. Once accepted and merged, the changes are pushed to our routers within a few minutes.

Pull Request: routedbits/dn42-peers#122

Let us know if you have any questions or issues.

Thanks,
NOC, RoutedBits