At last check the i6000 doesn't boot with other controllers installed. The next steps will be to monitor the serial output during a normal boot and then compare that with other line card boots.
The i6000 arrived yesterday. It's unpacked, off the skid, and in the garage. After putting a few bolts back in (holds the two chassis together) and bolting a few other things back on it's powering up and robotics are on. It shows as online.
However the drives aren't showing up. The UI indicates a few issues probably related to the CAN bus. That all seems connected though. So I'm not sure what's up right now.
In the interest of being a good netcitizen I've removed some of my i2000 and i6000 related posts. Baring any issues I'll probably repost them on/before 2019-01-14.
If you're using a Quantum, Dell, or ADIC Scalar product you should check to see if the password of the GUI's 'service' account is static. If it is then there is a pretty trivial way to get into the system using the vendor's maintenance account. The one system I have access to, an i2000, has a login of service:10101100.
If you're using a Quantum, Dell, or ADIC Scalar product you need to make sure the 'service port' isn't remotely accessible. If it is then there is a pretty trivial way to get into the system as 'root'. The port is explicitly listed in the manual as not for "normal" use.
tl;dr If you aren't plugging in stuff you shouldn't (per manual) then the risk isn't that bad.
Thanks to my sister and her husband my tape libraries will now be the "Gibsons". I think I'll go with gibson2 and gibson6 for hostnames. Non-sequential just to mess with people...
My yum mirrors are back up and stable. Although they're 100% on my home infra atm. Long term I plan to use an OVH-Virgina set of VMs to act as caching proxies before hitting my home.
Protocols Supported: HTTP & HTTPS