Page 1 of 1

[Solved] INTERACTION_ERROR after hostname change on Cisco

Posted: Thu Oct 30, 2025 3:28 pm
by cschnappinger
Hi,

I'm having troubles doing a mass-config push. In my template I'm changing the hostname of a device. Afterwards I'm receiving a "INTERACTION_ERROR" and the push stops. A second push - after the hostname is set - is successfully..
May someone have any ideas how to fix that ?

thanks a lot
Christian

Re: INTERACTION_ERROR after hostname change on Cisco

Posted: Thu Oct 30, 2025 4:53 pm
by jozef
Hi Christian,

When Unimus interacts with devices, it typically learns part of the device prompt, usually the hostname, for more precise detection. If your device includes the hostname in its prompt and you change the hostname during an MCP, Unimus may fail to recognize it, resulting in an INTERACTION_ERROR.

You can resolve this by changing the prompt detection method in your MCP preset → Advanced settings → Prompt. Set it from Learning to Simple.

Re: INTERACTION_ERROR after hostname change on Cisco

Posted: Fri Oct 31, 2025 6:28 am
by cschnappinger
HI Jozef,

thanks for your reply.. I'll give a try ! :)

regards

Re: INTERACTION_ERROR after hostname change on Cisco

Posted: Mon Nov 10, 2025 9:27 am
by cschnappinger
Hi Jozef,
we tried to set the method SIMPLE and get the following error (see attachement)
may you have any ideas for fixing ?
thanks a lot !

Re: INTERACTION_ERROR after hostname change on Cisco

Posted: Mon Nov 10, 2025 11:57 am
by jozef
Hi Christian,

Unimus does not recognize the promptMatchingMode property. Specify it as promptMatchingModeEnum instead.

You can access the available v3 endpoints using the built-in Swagger UI at:
http://your-unimus-ip:8085/api/v3/ui

Re: INTERACTION_ERROR after hostname change on Cisco

Posted: Tue Nov 11, 2025 7:31 am
by cschnappinger
HI Jozef,

works perfectly, thanks a lot !

Regards