Scenes
The local HinemosServer monitors servers in different regions (Japan, Singapore, India). For some reasons, the local HinemosServer needs to be migrated to the public cloud AWS.
Migration steps
1. Mirror the local HinemosServer (ova file)
2. Upload the created ova file to S3
3. Convert the ova file in s3 into an AMI file available to AWS
4. Create a new HinemosServer (EC2) from the converted AMI file
5. Start the newly created HinemosServer and start the Hinemos service
6. Use HinemosClient to connect to the new HinemosServer, if there is HinemosAgent monitoring,
At this point, it can be found that all states are dangerous
(At this time, in order to cause unnecessary trouble, it is best to turn off the email notification)
7. Log in to the monitoring node and modify some configurations so that the new HinemosServer can monitor the node
Modifications:
1) Security policy includes local firewall and outer firewall (port 161)
After the modification is completed, you can confirm whether the network is smooth through snmpwalk
snmpwalk -v 2c -c public xxx.xxx..xxx..xxx .1
2) If HinemosAgent is installed, you need to modify the Agent.properties file
Modify the managerAddress and change the old HinemosServer address to the new address on Aws.
3) Restart the hinemosAgent service
sh /opt/hinemos_agent/bin/hinemos_agent_stop.sh
sh /opt/hinemos_agent/bin/hinemos_agent_start.sh
8. Confirm the monitoring status in HinemosClient