ilinkacc: $ cat /proc/cpuinfo
processor : 0
cpu : 440GP Rev. C
revision : 4.129 (pvr 4012 0481)
bogomips : 593.92
vendor : ADIC
machine : MCB
While looking through extaccess.conf I found this:
## Engineering mode, enable everything
Might be worth checking out.
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.
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.
- Connect to the service port
- It's that little black covered on that says not to use
- Set your ip to 10.10.1.100
- The last octet can be anything but .1
- Use 'telnet' to connect to 10.10.1.1
- Login with "root" and "dallas"
I found this by using john the ripper on /etc/shadow in 10.10.1.1:/tftpboot/cmboot/initrd-dmcb (NFS). The initrd is gzip'ed. Once unzipped you can mount it with a loop device.