Once a mbox is properly licensed and becomes online, it will initiate a contact to mfusion server and start monitoring automatically.
On the mfusion side, the mbox has to be added to the system, and assigned to the respective customer groups.
There’re a few key parameters to be provisioned for a new mbox monitoring:
Hostname (this should be the MAC address of mbox eth0 interface, in the format of xx-xx-xx-xx-xx-xx). Note all alphabet characters have to be in lower case.
Port number: Each mbox will have a unique port number, assigned as part of the licensing parameters.
Monitoring template: Choose the correct template type for your mbox, depending on its respective model (eg. CMG, HSG, or HSA).
Monitoring probe: Choose the respective probe to monitor this mbox host, typically the cloud probe.
A few things to check:
1. Is mfusion agent running? Console or SSH into mbox from the mfusion portal (if you configured the correct port number, you should be able to do this, otherwise you should troubleshoot if mbox is really “online” in the first place). Under the “enable” mode, issue command “show mfusion agent” to check if mfusion agent is running.
NOTE: If mfusion agent is not running, you probably don’t have the correct license and should contact RansNet support for help.
2. If mfusion agent is running, but still did not turn green after more than 5 minutes. You should now check if the “hostname” parameter is correctly configured. The “Host name” part of the host config on mfusion is case sensitive. Make sure to use all lower cases for any alphabet characters.
3. If mfusion is running and the hostname is correct, but still not working. Need to check if you’ve selected the correct monitoring probe to monitor your mbox. If you add a new host from the wizard, by default, no probe is assigned (that’s why it’s recommended to clone an existing mbox config and just change the hostname and port no.