Wednesday, February 15, 2017

vCenter 6.0 Failed To Deploy .OVF

So today I ran into an issue where I was exporting to template, a Cent7 image from vSphere 5.5 and importing into version 6.0.

I exported successfully enough, which generated three files: cent7-base template.ovf, *.vmdk and *.mf.
I needed to get these files from our ESXi server in-house to the states datacenter across a semi-quick VPN tunnel.  So I was able to browse the datastore in 6.0 and upload the three files from my local machine.

1.58 hours later..

Done.  So feeling good about myself I went to import OVF Template only to have it fail roughly 5 seconds later.  The error was: _deviceimage-0.iso was not found

Puzzled.. wait how the hell was there an iso involv... oh crap.  I forgot to disconnect the pending/failed VMware Tools installer.  So being the curious lad that I am, I (on a guess) tried opening the ovf file using Notepad.. primarily because it was small and I figured it might hold config info.  Boy was I right!  The .ovf file is laid out like an XML.. I found one reference to an iso file.. specifically: vmware.cdrom.iso.  So I removed it and instead placed the following: vmware.cdrom.passthrough which I recalled was an option in the GUI.

Saving the file I re-tried teh import to have it complete successfully!  WOOT.

Friday, January 27, 2017

MobaXterm, Where have you been all my life?

MobaXterm... I discovered this beauty two weeks ago and I must say, wow.

At my 'new' job, (I emphasis that because I've been here 4 months now) anyway I support almost 40 various Linux servers and like 10 Windows machines.. all virtual of course.  But needless to say the majority of my time in in a terminal.

So anyway I started using SuperPutty like my co-worker, the other SysAdmin.  SuperPutty is alright, I mean it's got tabs, you can paste easily enough, saved links imported from Putty.  However I just had this feeling like I was missing out.  I mean its' 2017 FFS! There's better (i.e. more feature-rich and prettier) stuff out there.

So I went Googling and MobaXterm is the result.  It's so good that my boss today decided to buy a trio of licenses.

What do I love about it?  Well it did teh same as SuperPutty, it imported my saved sessions, it's got session tabs.. but it also supports connection ranging from ssh to sftp, serial, http, telnet, rsh, rdp, vnc, ftp, mosh, browser and more! It has what they call a 'graphical SSH browser' that sits along the left-hand side that allows you to browse the fille/folder structure.. even copy files to and from the host.  Or you can directly edit files within the same window.. This alone allowed me to ditch WinSCP!
Oh man.. and Syntax Coloring, there's typical Linux, Warnings/Errors, Cisco and  a couple more.  And what I noticed right off the bat, upon successful connection to a remote host you are presented with a window that tells you the following:
X11 Forwarding enabled?
SSH Agent?
How many Active SSH tunnels to this host
and the X11 Display IP

I'm not a paid spokesman by any means.. but damn this is one friggin awesome product!


Thursday, January 26, 2017

Rescan Linux VM guest for new vmdk w/o reboot

So recently at $work I've been handling a project to migrate production and test Oracle environments to new hardware on top of new vSphere as well.

So my job is corralling the DBA contractor, keeping him on par and whatnot.  Anyway this post isn't about that really.  The servers themselves are CentOS 7 with Oracle 12c, and in the name of Best Practices I've created 5 hdd's: OS, U01, U02, tmp and Backups.  So last night DBA requests another named U03 to house teh redo log files.  Ok sounds good, but this time I did not want to have to bounce the server to see the hew 'hardware'. So credit goes to: Vivek Gite @ here

echo "- - -" > /sys/class/scsi_host/host#/scan

Works like a friggin champ!  Of course this string returns nothing but a quick Fdisk -l shows that my sdf was found.

*drops mike*

Tuesday, December 27, 2016

Viper 4105V install, 3rd Gen Dodge Ram 1500

So living in a northern climate makes you appreciate any little thing that can keep you from unnecessarily going outside during winter.  Hence, a remote start.

I recently bought a 2003 Ram 1500 quad cab SLT 4x4 that luckily came with a topper but no keyless and no remote start.  I still think its odd beacause my old 2000 Sierra came with keyless, auto-headlights and no distributor cap/rotor. (That's a whole 'nother gripe)

Anyway I picked up a Viper 4105V Remote Start and Keyless system this past week at a steal! Too good to pass up.  No unbeknownst to me is that Viper is HORRIBLE at instructions. Their systems are sold to consumers but you are expected to get it professionally installed.  They will not give you more detailed instructions for the actual install than a pinout and a very short descriptor of what each wire does.  It's up to you to obtain a wiring diagram for your vehicle and translate their descriptions to match teh wiring in your vehicle.

Anyway after much trial, some error and a few wise tidbits from I completed the install in about 6 hours.  (With food and beer breaks).

So below is an ugly table of my findings, hope it helps someone. Oh BTW my truck does not have a transponder key, if yours does you will have to get a bypass module.

pin number - color - description - ram wire

Pri Harness

1 Light green black - 200ma factory alarm disarm - NOT USED

2 Green/white - 200ma factory alarm arm - NOT USED

3 yellow - ignition out - To Heavy 6 NOT USED

4 white/blue - activation output - NOT USED

5 orange - 500ma ground when locked - NOT USED

6 brown - 200ma horn output - black/red steering column

7 red/white - trunk release - NOT USED  (Might use this for a tailgate lock)

8 black - ground

**9 white - light flash - purple/yellow @ headlight switch with relay and 330 ohm resistor

Remote start harness

1 black/white - parking brake - ground

2 purple/white - tach - injector or coil wire Any wire other than teh green wire on the coil

3 brown - brake shutdown - white/tan above brake pedal

4 gray - hood pin - ground when hood shut

5 blue/white - 200ma rear defogger - NOT USED

Heavy Gauge Relay Harness

1 red - 12vdc input - red/white steering column

2 pink/white - Second ign/accessory out NOT USED

3 red - 12vdc input - red/white steering column

4 orange - accessory input - orange steering column NOT USED

5 purple - starter output - yellow steering column

6 pink - ignition 1 input - steering column NOT USED

Door Lock*

1 blue - -200ma unlock out - blue driver kick panel

2 empty

3 green -200ma lock out - tan/pink driver kick panel

Satellite Harness not used

D2D (I dont even know what this is) likely unused

Bitwriter harness not used

* used 2 x relays, unlock needs 330ohm resistor, lock needs 820ohm. (I used 330 and 1k and it works)


I sent an email to Viper's customer support, I had heard they would not help you unless you are an authorized dealer. That's rumor turns out to be true. If you won't offer support then why sell on Amazon??

Type your response ABOVE THIS LINE to reply

Benjamin Hart

Subject: - Customer Feedback/Question

DEC 27, 2016 | 03:17PM PST
Ashley replied:

Good Afternoon,

Thank you for contacting Directed Electronics Consumer Support. Unfortunately we only provide installation and troubleshooting support on this product if you are an authorized dealer. Please take the vehicle back to an authorized dealer. You can go to and use the dealer locator tool to find your nearest authorized dealer.

This policy is in place to ensure that Directed Electronics is not held liable for damage caused by improper installation of this particular product.

Directed Electronics Consumer Support Team


Best Regards,

DEC 25, 2016 | 02:57PM PST
Original message
Benjamin wrote:

Name: Ben
Email Address:
Phone Number: 123-555-1212

Attention to Directed Department: Customer Service

Feedback/Question: I just bought a 4105V and I have a few questions. A. What is the purpose of the Satellite harness? B. What is the purpose of the D2D harness? C. Do you produce an actual Install guide, not vehicle specific, but the Quick Reference Install Guide kinda sucks. It's helpful but not a ton for self-installers. Thanks!

This email may contain confidential and/or privileged information. It is intended only for the person or persons to whom it is addressed. Any unauthorized review, use, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email or telephone and destroy all copies of the original message.

This message was sent to in reference to Case #: 129381.

Last reply.. warranty null and void.

Subject: - Customer Feedback/Question

DEC 28, 2016  |  04:04PM PST 
Ashley replied:

We do not sell our products to anyone but authorized dealers. If you bought this module from Ebay, Amazon ect., unfortunately, the device's limited warranty is immediately voided. As stated on our website, we only advise professional installation from authorized dealers as they are specially trained on how to install our devices. We are unable to guide an individual through installation due to liability issues. Please proceed to an authorized dealer.

Please go to the link below and you will be able to find an authorized dealer in your area.

If you have any other questions, please feel free to call or email.

Thank you for your patience,
Directed Electronics Consumer Support Team

Best Regards,


If you care about a warranty, DO NOT BUY VIPER PRODUCTS and install yourself.

Wednesday, December 7, 2016

Linux One-Liner in YAML (Ansible format)

So the linux config one-liner I posted yesterday.  Here it is in a workable Ansible playbook format:

- hosts: all
  name: Run the massive config one-liner
  become: yes
  - shell: set -x; history ; last  -n 666 -a -d -x -F ; who ; uptime ; uptime -p ; cat /etc/red-hat/release ; uname -a ; iptables-save ; netstat -tunap ; ps aufx ; yum list installed ; chkconfig --list ; chkconfig --list | grep on ; cat /etc/passwd ; cat /etc/group ; cat /etc/ssh/ssh_config ; cat /etc/ssh/sshd_config ; cat /root/.ssh/config ; cat /root/.ssh/authorized_keys ; cat /root/.ssh/known_hosts ; cat /home/*/.ssh/known_hosts >> /root/"$HOSTNAME"_"$USER"_`date +%F`.log 2>&1