Blog Just another tech site

11Apr/150

Zabbix User Parameters For Monitoring OSX Battery

Zabbix Graph
UserParameter=ChargeRemaining,system_profiler SPPowerDataType | grep "Charge Remaining" | awk '{print $4}'
UserParameter=FullyCharged,system_profiler SPPowerDataType | grep -m 1 "Fully Charged" | awk '{print $3}' | awk '{ gsub("No","0"); gsub("Yes","1"); print $1}'
UserParameter=ChargingStatus,system_profiler SPPowerDataType | grep -m 1 "Charging" | awk '{print $2}' | awk '{ gsub("No","0"); gsub("Yes","1"); print $1}'
UserParameter=FullChargeCapacity,system_profiler SPPowerDataType | grep "Full Charge Capacity" | awk '{print $5}'
UserParameter=CycleCount,system_profiler SPPowerDataType | grep "Cycle Count" | awk '{print $3}'
UserParameter=Condition,system_profiler SPPowerDataType | grep "Condition" | awk '{print $2}'
UserParameter=Amperage,system_profiler SPPowerDataType | grep "Amperage" | awk '{print $3}'
UserParameter=Voltage,system_profiler SPPowerDataType | grep "Voltage" | awk '{print $3}'

Calculated item within zabbix for battery percentage:

last(ChargeRemaining)/last(FullChargeCapacity)*100

Filed under: Uncategorized No Comments
8May/140

Billion BiPAC 5200 RC SNMP OIDs

BimgBillion BiPAC 5200RC

 

It surprised me that such a cheap router supports SNMP out of the box. Below are a handful of OIDs that may be handy for others.

 

Hardware Description: 1.3.6.1.2.1.1.1.0

System Uptime: 1.3.6.1.2.1.1.3.0

LAN IP: 1.3.6.1.2.1.4.20.1.1.10.1.1.1

LAN MAC Address: 1.3.6.1.2.1.2.2.1.6.1

Interface 1 In Bytes: 1.3.6.1.2.1.2.2.1.10.1

Interface 1 Out Bytes: 1.3.6.1.2.1.2.2.1.16.1

WAN In Bytes: 1.3.6.1.2.1.2.2.1.10.2

WAN Out Bytes: 1.3.6.1.2.1.2.2.1.16.2

Filed under: Uncategorized No Comments
27Apr/140

Synology DSM 5.0 SNMP Interface Statistics OIDs

3Ece9xL

 

I was looking statistics to be pulled through SNMP for a Synology NAS and walked across the following OIDs. I imagine hardware with more than one interface, the numbering will just follow along logically. I will test this at a later date.

1.3.6.1.2.1.31.1.1.1.1.1 - Interface Name - Loopback
1.3.6.1.2.1.31.1.1.1.1.2 - Interface Name - Eth0

1.3.6.1.2.1.31.1.1.1.6.1 - Interface RX Total Bytes - Loopback
1.3.6.1.2.1.31.1.1.1.6.2 - Interface RX Total Bytes - Eth0

1.3.6.1.2.1.31.1.1.1.10.1 - Interface TX Total Bytes - Loopback
1.3.6.1.2.1.31.1.1.1.10.2 - Interface TX Total Bytes - Eth0

1.3.6.1.2.1.31.1.1.1.7.1 - Interface RX Total Packets - Loopback
1.3.6.1.2.1.31.1.1.1.7.2 - Interface RX Total Packets - Eth0

1.3.6.1.2.1.31.1.1.1.11.1 - Interface TX Total Packets - Loopback
1.3.6.1.2.1.31.1.1.1.11.2 - Interface TX Total Packets - Eth0

1.3.6.1.2.1.55.1.5.1.4.1 - Interface MTU - Loopback
1.3.6.1.2.1.55.1.5.1.4.2 - Interface MTU - Eth0

1.3.6.1.2.1.55.1.5.1.8.2 - Interface MAC Address - Eth0

Filed under: Uncategorized No Comments
30Jun/120

Running Windows 8 Consumer Preview on VMWare ESXI Host

ESXI 5 Host Windows 8 Error

Due to the release of Windows 8 consumer preview and the final releases imminent release I have needed to do some testing of custom tools under my development at my place of work. I figured instead of going through the hassel of installing on a physical machine and tying up that machine for a while I may as well put it on one of our IBM Blade servers running VMWare virtual hosting.

I was keen to try this and loaded up the installation in a new virtual machine but it seemed to error on the installer booting, under both 32 bit and 64 bit installations. After some research on VMWares website it seems that a solution is available for running it on a VSphere / ESXI 5 host.

To resolve the error:

  1. Install VMWare hotfix ESXi500-201112001 (Patch 02) which can be found here (I believe it can be installed through VSphere update manager or manually on the host itself. Full instructions are included on the patch release page.)
  2. Create a new Virtual Machine on the host, with the operating system listed as Window 7 or Server 2008 R2. Make sure to use the E1000 network adapter, as the others malfunction.
  3. Install Windows 8 by attaching the DVD image like normal.
  4. Just a note VMWare tools within the guest operating system should function normally with Windows 8, but installation needs to be initiated manually.
24Jun/120

Links to Foscam IP Camera Firmware Updates

Foscam

I have noticed that Foscam seems to force registrations to gain access to the firmware upgrades. This link is to bypass the forced registration.

http://foscam.com/down3.aspx

In the menu bar the latest software, manuals and setup guides can also be accessed. These firmware upgrades can also be used on unbranded Foscam cameras.

11Jun/120

BlackBerry PlayBook Setup Issues

The dreaded failed update....

I recently received a BlackBerry Playbook and had a hell of time time getting the initial setup to function.

The PlayBook forces updates on the first boot and setup, which seemed to work fine initally in Australia, but the estimated time was over 5 hours. After about 2 hours, it stated a connection error and tried to restart. From then on, it would show connection to update server failed, with multiple error codes such as 2011, 3001.

After some research online, I found a manual update method through the BlackBerry Desktop software, which makes the computer think there is an issue with the device and needs to be reloaded (Warning, this will wipe the device if It has previously been used):

  1. Install the BlackBerry Desktop Manager Software found here
  2. With the PlayBook powered on, plug it in to the computer to allow drivers to be installed.
  3. After they are done, power off the PlayBook (Holding down the power button on the top).
  4. Make sure the BlackBerry Desktop Manager software is open
  5. You will have to be quick for this, power on the device and watch for an option to update, this will only show for a few seconds.
  6. Follow the prompts to update and let it download and install, this took about 4 hours on an ADSL2+ connection, I figure there are no update servers in Australia.

This method partially completed the first time I tried, but must have lost the connection. When I retried this method it stated there were no updates found, even after trying this on several computers.

This left me no option then to call BlackBerry Support, which were very good and I would recommend if anyone else has issues.

Support stated that with the older OS versions, such as 1.0, there are issues connecting to the update servers so the method above was recommended. There was a bit of back and forth about this method stating there were no updates available and I was told in rare cases a file had to be removed from the program files.

C:\Program Files (x86)\Common Files\Research In Motion\AppLoader\Vendor.xml

After this file was removed the update through the computer was successful and I could finally start using the PlayBook, which seems to be a nice device so far from my experiences, but lacking on software somewhat.

Filed under: Uncategorized No Comments