Gp's Tape Infrastructure!
After being powered off and unplugged for a few weeks the CAN issue that I'd been having with the i6000 seems to have resolved itself. However the LTO-6 tape drive/sled I have isn't powering up at all. IDK what's going on with that. The error is that the barcode on the drive isn't recognized. This is caused by the system not having the drive registered via the system bus. Which in this case is caused by the sled not powering up.
The i6000 is on holding pending the end of FRC Build/Competition season. RoboLoCo is doing well so far this year but mentoring is a massive time sink. Oh well, ton's of VTO for me!
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.
Need to look into "/usr/sbin/eclicmd.pl" more - looks like it could be useful.
If you want to find a copy of the .pkg (used for software upgrades and such) of a box you already have, check out "/rollback/usr/local/amc/app/updates/".
To capture a standard snapshot you can run this from the CLI...
/usr/bin/perl /usr/bin/capture_snap_shot.pl -a -c -f /tmp/snapshot.tgz
The robot in the i2000 is powering up and moving. It's getting caught up in a few places and I'm getting a low voltage warning too. Gotta figure out if it's the cable chain, the tracks (bottom bar was bent up a bit), or the robotics module that has all of the motor controllers in it.
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.