Can't get the Marwatch Probe to start on MiCollab server

[AH64Armament]

I had to upgrade a MiCollab server to the latest today. This involved a fresh install and double-restore.

Along the way, I manually installed the Marwatch Probe software.
I've set it to register to the Host with the proper pin, but I can't get this to show "started" on the MiCollab blade.

On an MBG, I can mount the iso to /mnt/cdrom, then go to the servicelink/blades tab and manually install the blade from there.. and even uninstall it.
I know there is a way to have the MiCollab show the blades tab similar to MBG, but I can't seem to find the command or the URL.

I don't see anything in the logs pertaining to the MPA.

I'll try and open a ticket with Mitel support tomorrow if I need to, but figured I'd check here first.

 

[TheMaskedMagician]

Copy MW installer to a MSL /root directory

run these on SSH
cd/root
mkdir -p /mnt/cdrom
mount -o loop /root/Your-MarProbe-Installer-name.iso /mnt/cdrom
MarwatchVersion=$(ls -d /mnt/cdrom/Software/6000MAS/*/ | xargs -n1 basename)
install_blade --cdrom $MarwatchVersion
umount /mnt/cdrom
rm -rf /root/Your-MarProbe-Installer-name.iso

It will now be installed as a blade, completing the MPA config.

Hope this helps

 

[AH64Armament]

Copy MW installer to a MSL /root directory

run these on SSH
cd/root
mkdir -p /mnt/cdrom
mount -o loop /root/Your-MarProbe-Installer-name.iso /mnt/cdrom
MarwatchVersion=$(ls -d /mnt/cdrom/Software/6000MAS/*/ | xargs -n1 basename)
install_blade --cdrom $MarwatchVersion
umount /mnt/cdrom
rm -rf /root/Your-MarProbe-Installer-name.iso

It will now be installed as a blade, completing the MPA config.

Hope this helps

Are those updated commands to install this? here's the process I've used in the past, and used in this case too.

I pulled the lastest available iso from the probe software tab on my Marwatch account, and copied it to the system /root directory.
mkdir /mnt/cdrom - your command shows "-p" - I'm not sure what that is.
mount -o loop BLADE-FILENAME.ISO /mnt/cdrom
ll /mnt/cdrom/Software/6000MAS to show the installer on the /mnt/cdrom, then highlight the installer file.
install_blade -cdrom <right click to enter the installer file name.
When finished installing...
signal-event app-post-install
umount /mnt/cdrom

Then go to the /server-manager and configure the system to use it.

At this point, I'm wondering how to uninstall the blade to try and start over.

 

[AH64Armament]

Copy MW installer to a MSL /root directory

run these on SSH
cd/root
mkdir -p /mnt/cdrom
mount -o loop /root/Your-MarProbe-Installer-name.iso /mnt/cdrom
MarwatchVersion=$(ls -d /mnt/cdrom/Software/6000MAS/*/ | xargs -n1 basename)
install_blade --cdrom $MarwatchVersion
umount /mnt/cdrom
rm -rf /root/Your-MarProbe-Installer-name.iso

It will now be installed as a blade, completing the MPA config.

Hope this helps

I ran the commands as given and I'm still showing the Probe service status as "STOPPED".

I checked the Web Services and made sure the following are set for the Marwatch Probe:
Lacking next necessary permissions for the mpa-probe consumer:
/mbg/v2/globaloptions/: read=true
/mbg/v2/metrics/: read=true
/mbg/v2/siptrunks/: read=true
/mbg/v2/icps/: read=true
/mbg/v2/devices/: read=true
/mbg/v2/subscribe/: read=true, write=true

under the web services, there's a ton of tokens specific to Marwatch. Many are expired, but there's a lot that are active.

 

[TheMaskedMagician]

After running the commands successfully, you will need to go the MPA blade in MSL and configure the Probe settings.
Have you done these - setting the Hostname and PIN?

Services will remain Stopped until this is configured correctly.

 

[AH64Armament]

After running the commands successfully, you will need to go the MPA blade in MSL and configure the Probe settings.
Have you done these - setting the Hostname and PIN?

Services will remain Stopped until this is configured correctly.

Yes, I set that with the updated pin. Still shows stopped.
I've also stopped and restarted it.

Marwatch support has always been very helpful until the past couple of years when Mitel pulled it into their view as MPA. Since then, they tell me to contact Mitel support.
Mitel support won't talk about it unless you're certified. A few years ago, that course was $1200 - a cost that at the time, we couldn't justify.
I just looked again, and MPA 3.5 is now a self-study course that's free. I've enrolled and will start it later today.

 

[TheMaskedMagician]

You seems to have done all that is necessary for this to work.
From all the ones I have done, I don't need to make any changes to the Web Services.
Just need to make sure that MSL is able to resolve to the Marwatch Hostname and there's routes to it via the below ports - telnet or ncap should do the trick to test this.

SNMP: UDP, port 161,162
HTTPS: TCP, port 443
MCD Miscellaneous, TCP, ports 1752, 15373
FTP: TCP, port 21
SSH: TCP, port 22
ICMP: ICMP Echo

If nothing else works, I suppose Mitel Support is your next life raft.
Needless to say, in the past, I have also seen a reboot fixes it following the install.

Good luck.