How to Install SNMP on UnRAID6

One of the things I like to have in my lab environment is the ability to monitoring all OSes and keep an eye on such things as temperatures, disk space, and other sensors.  I was disheartened to find that UnRAID 6 did not have SNMP installed or configured. After some searching I was able to figure out how to get SNMP installed.

First, Log into your UnRAID Web page and Click on Plugins

Capture.PNGNext copy and paste the NerdPack Plugin into the URL Field and Click Install.  The NerdPack installs the prerequisites that you need to install SNMP.  Then you will see a plugin window pop up.

Capture.PNG

Then we go and reboot the server.  This step is not necessary, but I prefer to do this after each plugin install.

Next go to Settings, and Nerd Pack

Capture.PNG

Find the entry for Perl and click the slider

Capture.PNG

Click Apply on the bottom

Capture.PNG

The package manager will launch a window and you see the package install.

Capture.PNG

Then we go and install the UnRaid SNMP Plugin following the same steps for the previous plugin install.

Capture.PNG

Login to the host via SSH console and verify that SNMP is working by executing

snmpwalk -v2c -c public localhost

You should see output similar to below.

Capture.PNG

Now you should be able to import your host into an SNMPD Based monitoring.

Capture.PNG

No 10gbe NICs showing in VMware 6.X with X10SDV-7TP4F

When I started building my VMware ESXi server, I did not have a Switch that could handle 10Gbe SFP+.  Now that I have a Dell X1052, I figured I would cable up a 10Gbe DAC and get moving.  Much to my surprise, I received a link light on the switch, but not on the motherboard.

Capture.PNG

Digging into the VMware side, I noticed that the 10Gbe NICs are not available, only the 1Gbe NICs.

Capture

A quick Google search brought me to a great site for VMware knowledge, tinkertry.com.  It appears that the drivers for the 10Gbe are not loaded.  So following the directions here, we open the SSH Console and enter the following command.

esxcli software vib install -v https://cdn.tinkertry.com/files/net-ixgbe_4.5.1-1OEM.600.0.0.2494585.vib –no-sig-check

We then reboot our host to get the new VIB to be loaded.

Capture

Low and behold on reboot we see the two 10gbe NICs.

Capture

How To Setup a CentOS 7 Syslog Server

Today we learn how to build a syslog server.  Having a couple SuperMicro Builds, Switches and Firewalls, I want to be able to know what is going on by looking at one central source.   Easiest way to do this, and one that most Network Devices and SuperMicro Motherboards support is syslog.

First step is to build a quick CentOS 7 VM.  Next we install rsylog and other packages we will use later.  If you have installed the Minimum CentOS 7 image you will need the vim and net-tools packages.

yum install rsyslog vim net-tools

Next we open the syslog.conf file to allow the server to listen for syslog messages.

vim /etc/rsyslog.conf:

Then we un-comment the following four lines to allow syslog messages to be received on UDP and TCP Ports 514.

# Provides UDP syslog reception
#$ModLoad imudp
#$UDPServerRun 514

# Provides TCP syslog reception
#$ModLoad imtcp
#$InputTCPServerRun 514

becomes

# Provides UDP syslog reception
$ModLoad imudp
$UDPServerRun 514

# Provides TCP syslog reception
$ModLoad imtcp
$InputTCPServerRun 514

Then we restart the syslog service.

systemctl restart rsyslog.service

Then we want to verify that the service is listening on port 514.

netstat -an | grep 514

We should see that TCP is listening and that UDP is now showing for port 514.

Capture.PNG

Finally we want to allow TCP and UDP 514 through the firewall.

firewall-cmd –permanent –zone=public –add-port=514/tcp

firewall-cmd –permanent –zone=public –add-port=514/udp

firewall-cmd –reload

Now that we have the syslog server up and listening, lets configure one of our servers to forward its message.

For my SuperMicro servers, we log into the IPMI page and click on the Configuration Tab and then Syslog.  We click “Enable Syslog” and then we enter in the IP and Port for our Syslog Server.  Finally we click Save.

Capture

For ESXi we need to login to the CLI of each ESXi host and run the following command, replacing the below IP with your syslog IP.

esxcli system syslog config set –loghost=’tcp://10.11.12.13:514′

Capture

For me Dell X1052 Switch, we log into the Administrator Web GUI and Click Log and Alerts, Expand Remote Log Servers, and Click Edit.

Capture

Then we click Add.

Capture.PNG

Then we enter the required information for our Syslog Server.

Capture.PNG

Eventually as events are generated you will see them in /var/log/messages on the your syslog server.  Once we configured our Dell Switch we saw the following message generated.

Capture

PRTG Install Instructions

I am a bit of a Monitoring junky, and while I am mostly fluent Microsoft’s System Center Operations Manager, Observium, and Nagios/Opennms I do have a passing interest in PRTG

For myself, my current Observium Install does not have the MIBs installed to monitor my Dell x1052 Switch, and I liked to see a little more into how the switch is performing.

PRTG is known for handling network gear from all manufactuers very well, so I was curious to see how it performs.

First step is to go to PRTG’s website and download a trial.  PRTG will provide you are 100% functional trial key.  From there you build you host for PRTG, which for me was a low powered Virtual Machine.  The installer is extremely simple, just put in the Trial Key and Trial Key Name and let it install.  Once installed you will see two Icons on your desktop. As an astute reader pointed out, you are limited to 100 sensors, but this is perfectly fine for a homelab.

Capture.PNG

You can navigate to your servers IP address (or host name), and select the default login.

Capture.PNGPRTG can be very busy and distracting, but lets focus on getting our Dell Switch monitored.

Capture

Let’s click on Devices and the Add Device

Capture

Then we select Network Infrastructure

Capture

Next we plug in a device name, and an IP.  There is more configuration that can be done ahead of time to auto-discover items, but we won’t go into that here.

Capture.PNG

Once your device pops up on the Main Page, click Auto Discover.

Capture

After a while, we will see the following sensors pre-populated.

Capture.PNG

In a future post, I’ll show how to add custom sensors to monitor CPU, Memory and much more your Network Devices and Switches.

 

Easy ESXi Patch Updates

If you are not familiar with v-front.de and you have a ESXi servers, you are really doing yourself a dis-service.  v-front.de maintains a repository of all ESXi updates and makes it very easy for you to update your servers when the newest patches come out.

Lately I have been having a series of interested GUI crashes with ESXi no matter what OS or Browser I use.  Knowing I was a bit behind on patches, I decided to update.

From their patching site I was able to grab the latest software profile and install it.  The steps are easy to do this and I will detail it here.

    1.  Enable the SSH Shell for your ESXi Host. At the Host Tab, click Actions -> Services – Enable Secure Shell (SSH).
    2. Going to the patching site and clicking on the latest update, v-front.de lists us the steps how to update our host.
      esxcli network firewall ruleset set -e true -r httpClient
      esxcli software profile update -p ESXi-6.5.0-20170404001-standard
      -d https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
      esxcli network firewall ruleset set -e false -r httpClient
    3. Reboot and then verify that the vibs have updated
      [root@esxi:~] esxcli software vib list | grep esx-base
      esx-base                       6.5.0-0.19.5310538                    VMware    VMwareCertified     2017-05-13
      [root@esxi:~] esxcli software vib list | grep esx-ui
      esx-ui                         1.18.0-5270848                        VMware    VMwareCertified     2017-05-13
      [root@esxi:~] esxcli software vib list | grep vsan
      vsan                           6.5.0-0.19.5310540                    VMware    VMwareCertified     2017-05-13
      vsanhealth                     6.5.0-0.19.5310541                    VMware    VMwareCertified     2017-05-13

VMWare ESXi Passthrough and Freenas

I recently had user colicstew comment that they could not get Freenas 9.10.2 U3 to see drives on his LSI2116.  Luckily I have some unused 2TB Drives and LSI 2116 Controller as part of my Xeon D Lab.

IMG_0561.jpgIMG_0560.jpg

First step was to passthrough my LSI2116 Controller and Reboot the Server.  You should see Enabled/Active for the LSI Controller which we do

Snip20170511_1.png

Next I created a VM. Snip20170511_2.png

I chose to install the OS on one of my VMware Datastores.

Snip20170511_3.png

On the Hardware Settings I set as shown.

Snip20170511_4.png

Then I clicked Add other device -> PCI Device and Add the LSI ControllerSnip20170511_5.png

Finally I added a CD-ROM Drive and attached the Freenas ISO downloaded from here.

Snip20170511_7.png

Snip20170511_8.png

Finally we boot the VM

Snip20170511_9.png

Then we select Install at the first Screen

Snip20170511_13.png

One of the oddities I ran into while creating this tutorial was the key sequence to release the mouse from the VMWare Remote Console was the escape key in the Freenas installer that bounces you back to Initial Setup Screen, so the remaining pictures are via my phone.

On the next screen you will be warned about only having 4GB of memory.  Since I’m only using this as a test system, I am not concerned.  If you were running this as an actual file server you would want at a minimum 1GB of Memory per TB of storage.

IMG_0562.jpgOn the this screen we see five drives.  One is our drive we will install FreeNAS OS to, and the other four are 2TB Hitachi Drives I attached to the Xeon D Board.

IMG_0563.jpg

Next you are warned that FreeNAS will clear the drive you are installing to.

IMG_0564.jpg

Next you are asked to set the root password.

IMG_0565.jpg

Finally you are asked to choose a BIOS Mode.  

IMG_0566.jpg

At this point, I went to install the system, but no matter what I did, it would not install the OS, failing with the below error.

Snip20170511_15.png

The problem here is that the drive that we are installing the OS to is thin provisioned.  FreeNAS does not like this.

Snip20170511_16.png

Fix is to create the disk as “Thick provisioned, eagerly zeroed”.

Snip20170511_17.png

Once that was fixed, the OS installation continued without issue.

Snip20170511_18.png

Once completed, you will see the following success message.Snip20170511_19.png

Then, I chose option four to shutdown the system.  Be sure to remove the DVD Drive, or the system will continue to boot from the Installer.  Once that is completed your system will work as expected.

Snip20170511_23.png

Unfortunately, I had no issues getting the system up and running.  colicstew feel free to email me via the contact method and we can see about troubleshooting this issue.  I would start with verifying you have the correct breakout cable.  I used one of the four breakout cables from the Motherboard.

 

How to Enable SNMPD on ESXi 6.5

I had some difficulties enabling SNMPD from the GUI on ESXi 6.5 and kept recieving the following error

Failed – An error occurred during host configuration

Quick search let me here.

Running the below steps listed at the above link allowed me to start SNMPD in the EXSi GUI without issue

esxcli system snmp set -r
esxcli system snmp set -c YOUR_STRING
esxcli system snmp set -p 161
esxcli system snmp set -L "City, State, Country"
esxcli system snmp set -C noc@example.com
esxcli system snmp set -e yes