Important: Please use caution when adding engines to Avid NEXIS Systems
Recently a few customers have experienced media loss when attempting to add an engine to an Avid NEXIS System or create a new Avid NEXIS System in a network that already had Avid NEXIS. While the media loss was due to misconfiguration of the Avid NEXIS systems we are investigating additional protections but also wanted to re-iterate the correct steps to either add an engine or create another system in a network with existing Avid NEXIS.
Please refer to the manuals and readme available herehttps://avid.secure.force.com/pkb/articles/en_US/user_guide/Avid-NEXIS-Documentation
Adding an engine to an existing system
1. make a note of the IP address, system name <system-name> and version of existing system.
2. rack mount the engine, connect the 10G or 40G network interface, power up the engine
3. using a laptop connected to the 1Gb management port install same Avid NEXIS version as the existing system, reboot the engine
4. open the agent page and configure;
- Storage System Name: enter the SAME name as the system it is joining
- Enter a unique name for the engine and optionally an enclosure ID
- Do NOT check the box to “Run as System Director”
- Add the unique IP address for the 10Gb or 40Gb network interface(s)
- Click submit to reboot the engine to save changes
5. After the new engine reboots, login to the existing management console for the existing System Director, the new engine should appear with unbound Media Packs
6. Bind the Media Packs and Add to Storage Group as required
Do NOT create a new file system when adding an engine to an existing system
Creating a new Avid NEXIS system
When creating a new Avid NEXIS it must have a unique Avid NEXIS System Name and unique IP address. If other Avid NEXIS systems exist on your network make a note of any Avid NEXIS systems.
1. Note the IP address(es) system name(s) and versions of any existing Avid NEXIS in the network
2. Chose a unique IP address AND system name for the new system (system name CANNOT be the same as any existing NEXIS)
3. rack mount the engine, connect the 10G or 40G network interface, power up the engine using a laptop connected to the 1Gb management port install the current Avid NEXIS version, reboot the engine
4. open the agent page and configure;
- Storage System Name: enter a unique name (Not the same System Name as any other Avid NEXIS)
- Enter a unique name for the engine and optionally an enclosure ID
- Check the box to “Run as System Director”
- Add the unique IP address for the 10Gb or 40Gb network interface(s)
- Click submit to reboot the engine to save changes
5. After the new engine reboots, login to the existing management console for the System Director, the engine should appear with unbound Media Packs
6. Bind the Media Packs and create a Storage Group
7. Create Workspaces
8. Create users and assign permissions to users and workspaces
Do NOT use the System Name of an existing system when creating a new, separate Avid NEXIS System
Avid NEXIS Documentation https://avid.secure.force.com/pkb/articles/en_US/user_guide/Avid-NEXIS-Documentation
The most recent and recommended release is Avid NEXIS 2020.5http://resources.avid.com/SupportFiles/attach/AvidNEXIS/AvidNEXIS_ReadMe_v2020.5.0.pdf
and all systems recommended to be Avid NEXIS 2019.12 http://resources.avid.com/SupportFiles/attach/AvidNEXIS/AvidNEXIS_ReadMe_v2019.12.0.pdf or higher
. How can a professional company like AVID make such a bad tool.
-, I've passed through several plattform eras, like 68k, PPC, Intel... Windows... several competitors, like Discreet Logic Edit, Final Cut Pro, Edius, Premiere... I elected Avid's Media Composer and Pro Tools... and Mac - eventough I dumped Apple a few years ago, for sticking with the so called trash can and not being fond of a lot of their philosfies.
and limited by the lack of software support. Although the machine was powerful, it was rendered precociously obsolete.
