With Windows server this was a easy thing, but now, how to?

Does someone have a solution here?

It is currently not an option to have an UPS to shut down the NEXIS on the event of power loss. This is planned for a future release.

Bob, do you have a link to the procedure with ISIS?

Following up on this. No updates? :-) Not seeing anything in the latest documentation.

A core part of every Avid admin's existence is the dreaded late-night power outage... it's really something that can be automated. Hell, for those who want to be extra cautious, allow setting a permission schedule; so auto-shutdown is enabled off-hours only.

(15 years ago I set up a Mac online bay, with an APC UPS and a serial port shutdown link. The instant I plugged in the cable to the Mac, BAM, the UPS turned itself off and took the bay down with it.)

Still not a feature in NEXIS. Talk to your friendly Avid Sales person.

This would be a great feature.

We also have a UPS but it's useless when the power runs out beyond bussiness hours.

So please, because reliability is important, make it happen.

Regards,

I've heard that Avid think it's no big deal if the power runs out....no danger. (well, you maybe lose 14 mins work in worst case if auto save is set on 15 mins)

Maybe more important to have surge protectors.

I would like to speak to the person who said that. Was he serious? I suppose Nexis has a very secret feature that any vendor of hardware would want to implement. But Avid keeps it for their own use because.... well because that feature doesn't exist.

It's nonsense. Losing power is very bad for any server, including Nexis.

As of June 2023: Is it possible now to trigger a shutdown with Version 2023.3.0? I found a note in the Setup and maintenance guide regarding an UPS and in the Administration Guide there is a note regarding read-only SNMP monitoring. Is there something I might have missed?

Hi Christian, 
The only way I can think of is using a script that can be run from any linux host, to shut dows all system's engines. If you trigger such script with the UPS than technically it solves your problem. 
Plese note - although we tried this - it's not a formally supported procedure by Avid!

So just for those who know what they're doing:
The .sh script would be something like this (with your IP's and credentials of course )

#!/bin/bash

curl -k 'https://192.168.10.221:5015/agent?context=5815&r=avid_internal&type=shutdown&pass=XXXX' &

curl -k 'https://192.168.10.222:5015/agent?context=5815&r=avid_internal&type=shutdown&pass=XXXX' &

curl -k 'https://192.168.10.223:5015/agent?context=5815&r=avid_internal&type=shutdown&pass=XXXX' &

curl -k 'https://192.168.10.224:5015/agent?context=5815&r=avid_internal&type=shutdown&pass=XXXX' &

curl -k 'https://192.168.10.19:5015/agent?context=5815&r=avid_internal&type=shutdown&pass=XXXX' &

Hello Luke,

just tried this - works like a charm, thank you for letting us know. 

For anybody reading: Integrate a wait time after each command to shut the engines and media packs down in the correct order (the order the Admin / Maintenance Guide suggests). If you use the script as above without a waiting time in between it will fire all commands at once and you risk not getting them shutdown in the order as written.

Best regards,
Christian

From what do you execute the script? The UPS - a Standalone Linux Box or...?

Could I do it from a Qnap or Synolgy that already has a UPS on it?

I have the SNMP of my UPS trigger a script via SSH on a linux machine. That script triggers multiple other scripts to halt services and shutdown VMs, the NEXIS engines and sends out mails.