MT 3.1 - API Send fails with "<serno> not connected"

Reply
L3 Networker

MT 3.1 - API Send fails with "<serno> not connected"

Upgraded to 3.1, and attempted to send API to device which a minute earlier had been successfully refreshed.   The device is up, and answers API calls, however when MT 3.1 tried to send converted API, received failure notice as mentioned in subject.

--Felix

L7 Applicator

Re: MT 3.1 - API Send fails with "<serno> not connected"

Have you seen something in the new debug for the api?? /debug/api.php

L7 Applicator

Re: MT 3.1 - API Send fails with "<serno> not connected"

We are doing tests and we can send API calls against firewalls. Please validate connectivity and try to restart the VM.

L3 Networker

Re: MT 3.1 - API Send fails with "<serno> not connected"

Try the debug URI, too much info, locked browser (Chrome) up.

BTW, forgot to mention...target device is an M100 (Panorama).  Was adding post/pre rules and tags to a new Device Group.  The API call were Atomic but just for the security rules and tags.  Last time I was able to do this, I was still on MT 3.0.4.

--Felix

L7 Applicator

Re: MT 3.1 - API Send fails with "<serno> not connected"

We have fixed this weird behaviour in 3.1.1, please upgrade

Regards

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!