Remotely configure the network settings on an APC AP9617 management card
On windows:
Open a cmd window, Run as administrator Create an arp entry by specifying the desired IP address and the AP9617’s MAC address
arp -s 192.168.2.23 00-c0-b7-69-c2-84 Ping the new IP address with a buffer size of 113
ping 192.168.2.23 -l 113 In your browser visit the new IP http://192.168.2.23/ Note: Unless previously changed, the default credentials are: apc / apc
Just a matter of time Recently I started to receive notifications from FreeNAS indicating smart errors on one my hard drives. A quick check of the system log confirms a number of smart errors on /dev/da4.
root@freenas:/var/log # grep smart /var/log/messages Feb 1 03:39:51 freenas smartd[2739]: Device: /dev/da4 [SAT], previous self-test completed with error (read test element) Feb 1 03:39:51 freenas smartd[2739]: Device: /dev/da4 [SAT], Self-Test Log error count increased from 0 to 1 Feb 4 21:46:05 freenas smartd[48304]: Device: /dev/da4 [SAT], previous self-test completed with error (read test element) Feb 4 21:46:05 freenas smartd[48304]: Device: /dev/da4 [SAT], previous self-test completed with error (read test element) Feb 4 21:47:00 freenas smartd[48927]: Device: /dev/da4 [SAT], previous self-test completed with error (read test element) Feb 4 21:47:00 freenas smartd[48927]: Device: /dev/da4 [SAT], previous self-test completed with error (read test element) Feb 5 06:17:00 freenas smartd[48927]: Device: /dev/da4 [SAT], previous self-test completed with error (read test element) Feb 5 06:17:00 freenas smartd[48927]: Device: /dev/da4 [SAT], Self-Test Log error count increased from 1 to 2 Feb 5 06:17:00 freenas smartd[48927]: Device: /dev/da4 [SAT], previous self-test completed with error (read test element) Feb 5 06:17:00 freenas smartd[48927]: Device: /dev/da4 [SAT], Self-Test Log error count increased from 1 to 2 Pulling up the smart information available for /dev/da4 confirms the recent read errors.
2.2" SPI TFT Display Wiring Display Raspberry Pi GPIO VCC 3.3V GND GND CS CEO RESET 25 D/C 24 SDI (MOSI) MOSI SCK SCLK LED 18 SDO (MISO) n/a Note: The above wiring scheme is the default GPIO values used by the fb_ili9341 TFT driver. These can be customized if required using the gpios parameter in /etc/modprobe.d/fbtft.conf.
Raspberry Pi Configuration Reference: https://github.com/notro/fbtft/wiki
Create /etc/modules-load.d/fbtft.conf with the following:
spi-bcm2835 fbtft_device Create /etc/modprobe.
Wiring Button Pin RPi GPIO 1 GPIO 3 (SCL) 2 GND Power On On my Raspberry Pi 2 Model B Rev 1.1, the system will power on from a halted state when shorting the SCL (GPIO 3) to Ground.
Shutdown When the system is on, the below script will monitor SCL (GPIO 3) for a button press. When a button press is detected, the script will shutdown the Raspberry Pi safely.
Read through the preamble to see what I tried first and why it didn’t work. Or jump ahead to the working install method.
Preamble I’ve been using FreeNAS for a couple of months now, starting with version 9 and later upgrading to version 11. While the experience so far has been great there are a few glaring omissions. First and foremost “monitoring”. There is just no convenient way to monitor the system externally.
I run Plex media server in a FreeBSD based jail. Until now, to connect to the Plex system I would first ssh to the host system. Then I would run jls to find the jid of the jail.
# jls JID IP Address Hostname Path 1 - plex /mnt/vol1/jails/plex I could then connect to the jail system by passing the jid as an argument to jexec with the shell to execute.
My file server is sporting a SuperMicro X10SDV-4C-TLN2F-O motherboard and the case has two Noctua NF-R8 Redux-1800 PWM exhaust fans to keep things cool and quiet. However I noticed that whenever I set the fan mode in IPMI to Optimal, the fans began to pulse.
They slow down, IPMI decides they’ve slowed down to critical levels and spins them back up again. Having no reason to be spinning this fast, they slow back down and the cycle continues again.
