MBG Error when updating the Blades options

[DaveA]

Hi all, I have recently deployed two MBGs into Azure. The deployments went ok, I licenced both systems, then updated the MSL and downloaded and installed the MBG. But now in Blades I am seeing a 'transport endpoint is not connected' error for both systems. I can still sync with the AMC ok and its not a firewall issue otherwise I wouldn't have been able to download a new MSL or MBG. The error message differs slightly between systems, see one attachment, but they say:

'WARNING:   https://swdlgw.mitel.com/swdlgwapi/rpc connection error: Transport endpoint is not connected'. This one I rebooted and it now seems ok.
'WARNING:   Transport endpoint is not connected'. This one also rebooted but still get this error.

Any ideas?

Thanks

[dilkie]

hat sounds like a temporary error trying to access the blades server. The licensing server, AMC (soon to be SLS), is different from where the s/w is located and download from. SWDL (SoftWare DownLoad)

[DaveA]

No I dont believe it is as i have other MBGs that can access swdl absolutely fine, including my second MBG in Azure so to me this is most likely MBG related, somewhere?!?

[lundah]

Check the "messages" log file and see if there's any detail or helpful information there. I've never seen that error before.

[dilkie]

run tcpdump to see what the connection is failing at... looks like a network issue to me.

correction, i read the original issue wrong, thought you said the problem resolved after re-booting.