Here and there I post some interesting technical detail I run across, but this one will be pretty esoteric for most.
I currently manage several VMware Infrastructure 3i clusters (ESXi 3.5). I don't upgrade on a regular basis, because, well, these systems just run. They're not highly exposed (they're behind a firewall) and none of the host ports are exposed to the public internet. That said, an upgrade to VMware 4.1 is forthcoming!
As a result, I didn't become aware that VMware has a certificate on their systems against which patches are checked - and that this certificate was expiring in June 2011.
Using the VMware Infrastructure Update tool, I tried to update the ESXi systems I have at my DR site (in preparation to update those in production), and while one updated without trouble, the second failed, with "Signature check failed." in the esxupdate log (in /var/log/vmware/, if you're logged into the console on the host.)
Because this is an ESXi system, I didn't have the (relatively) easy RPM-based update mechanism that the ESX systems have, and all of what I could find from VMware indicated the same thing - that I needed to get the most recent version of ESXi 3.5 on an ISO, boot from that and perform the upgrade that way.
That seemed like way too much work, in particular because these machines are 1975 miles away from me.
The contents of the particular ESXi offline patch file I needed (ESXe350-201105401-O-SG, downloadable here includes three components - firmware, VMware Tools, and the Virtual Infrastructure Client.
The patch file is in a Zip format, though ESXi has no "unzip" tool, so I opened that archive and pulled out the three zip files it contained. The one that matters is the one with the firmware (in this case, ESXe350-201105401-I-SG.zip).
I extracted the folder contained within it (ESXe350-201105401-I-SG) to the desktop on my Windows workstation. I then uploaded the folder to a datastore reachable from the host.
At this point I verified that no VMs were running on the host, and I switched it to maintenance mode.
Not knowing what all I would need to execute in this directory, I got on the console (I enabled SSH a while ago), and navigated through the filesystem into the ESXe350-201105401-I-SG folder (in my case, it was in a folder off the root of a datastore called "DR-Test", so /vmfs/volumes/DR-Test/update/ESXe350-201105401-I-SG). The important script therein is "install.sh", and as it was not set executable (it was -rw-------), I performed a "chmod 755 -R ESXe350-201105401-I-SG", so the script could run.
I then ran the script (typing "./install.sh"). The script ran a quick filesystem check, then indicated progress with percentages (0%, 14%, 28%, ...). Once it was finished, I went back to the VMware Infrastructure Client and rebooted the host.
In a few minutes, I was up and running the new version ("vmware -v" showed "VMware ESX Server 3i 3.5.0 build-391406.
Let me know if this helps you!
Thanks to VMwareWolf for the good info.
Showing posts with label data. Show all posts
Showing posts with label data. Show all posts
10 August 2011
18 September 2008
Windows device cleanup!
Ever wonder how Windows remembers (read: doesn't need to install drivers every time you connect it) your USB drive, external monitor(s), DVD-ROM drive, etc? It keeps track of everything that it ever detected (through Plug and Play or otherwise).
Forever.
While researching VMware physical-to-virtual (P2V) and virtual-to-physical (V2P) conversion, I couldn't figure out why I kept receiving error messages about an IP address configured on an interface that was no longer in the system. I did some digging, and found this Microsoft KB article, which outlines the two-step process to finding all these hidden devices (which can cause some unintended conflicts).
Have a look at your system, and see just how much old junk you can pull out of there!
Forever.
While researching VMware physical-to-virtual (P2V) and virtual-to-physical (V2P) conversion, I couldn't figure out why I kept receiving error messages about an IP address configured on an interface that was no longer in the system. I did some digging, and found this Microsoft KB article, which outlines the two-step process to finding all these hidden devices (which can cause some unintended conflicts).
Have a look at your system, and see just how much old junk you can pull out of there!
23 January 2008
Stem the tide, and protect yourself!
We're all faced with two related problems. One is an overflowing number of offers for new credit cards, and concern about protecting your identity (and credit) from theft.
Stop that flood of inviting credit card offers with the help of the (generally not-so-helpful) big three credit reporting agencies. A link on the Federal Trade Commission website has some very helpful information on ways to stem the flow of offers. They also have links to the National Do-Not-Call Registry which should keep any legitimate commercial entities (with which you do not already have an existing relationship) from contacting you unbidden.
Not only does this keep junk out of your mailbox, it also provides fewer opportunities for those who might slip one out of your mailbox for untoward purposes.
Keeping a regular eye on your credit details and score can help you discover earlier any discrepancies in your record. Another link on the FTC website explains how you can receive (for free, annually) your credit report from each of the big three credit reporting agencies.
Also, for those who still pay regular bills via regular post, consider this reason for going online with your bill-paying. Those stamped envelopes you place in your mailbox (to await your letter carrier) are easy prey for those who can then empty out your checking account writing forged, duplicated checks. Pay electronically, or take those outgoing paper payments directly to the post office (or to wherever they'll be safely picked up by the post), not in your mailbox by the street.
Stop that flood of inviting credit card offers with the help of the (generally not-so-helpful) big three credit reporting agencies. A link on the Federal Trade Commission website has some very helpful information on ways to stem the flow of offers. They also have links to the National Do-Not-Call Registry which should keep any legitimate commercial entities (with which you do not already have an existing relationship) from contacting you unbidden.
Not only does this keep junk out of your mailbox, it also provides fewer opportunities for those who might slip one out of your mailbox for untoward purposes.
Keeping a regular eye on your credit details and score can help you discover earlier any discrepancies in your record. Another link on the FTC website explains how you can receive (for free, annually) your credit report from each of the big three credit reporting agencies.
Also, for those who still pay regular bills via regular post, consider this reason for going online with your bill-paying. Those stamped envelopes you place in your mailbox (to await your letter carrier) are easy prey for those who can then empty out your checking account writing forged, duplicated checks. Pay electronically, or take those outgoing paper payments directly to the post office (or to wherever they'll be safely picked up by the post), not in your mailbox by the street.
13 January 2008
Purge, purge, purge...
As a proper card-carrying technophile, I have collected far more than my fair share of electronics and other computer-related miscellany over the years. Since 1991, I have accumulated so much stuff that I have bins, boxes and drawers full of computer electronics with no current purpose... for anybody. Eventually, one gets to one of the big questions:
Just how many vintage-1995 PCI video cards does one need?
As it turns out, I don't need any.
Nor do I need ISA-bus modems - or, in fact, ANY ISA bus components whatsoever. Nor Socket 7 motherboards. Or that extra Pentium Pro system. Or those 30-pin SIMMs.
You're getting the picture. I need to get rid of a lot of stuff.
The purges have begun, with the shipment (finally!) of almost 50 pounds of cards, cell phones, mice, cables, etc. to Dell as part of their recycling program.
The realization that I needed to get rid of this stuff happened long ago, but it was made more... temporally important... by virtue of the new house (and the need to move all of our stuff from our old place. I didn't want to just toss this stuff out with our regular trash, because isn't the right way to dispose of all the lovely lead, mercury, cadmium and other nasties that lurk within all this gear. In searching around, I stumbled onto Dell's Recycling page and ordered two of their "Consumer Recycling Kit with one airway bill" for US$10.
Over the next 22 months, I collected many cards, motherboards and other not-so-goodies and filled a box - finally ending up with 49 pounds and 14 ounces of electronic junk, and shipped it off this past week.
I had occasion to look around again, and realized that I needed to send more. I had given the other "Recycling Kit" to my similarly-afflicted friend Brad Schutter, so I figured I'd just order up a few more. Returning today to the link I found via Google today resulted in immediate disappointment, however, as I couldn't find any links to that which I'd previously ordered.
Fortunately, despite my tardiness in using them, my order was still within the 2-year window into your order history that Dell allows, so I found the original Dell part number (310-6492) - and lo and behold, I found the page with the actual item.
Take stock of the old electronics you (or your company) have in your posession, and consider this viable (and valuable) option for getting rid of the now-worthless electronic clutter that a) you no longer need to keep around, b) you can't sell on eBay for US$0.01, and c) has no value to charities like The National Cristina Foundation.
Just how many vintage-1995 PCI video cards does one need?
As it turns out, I don't need any.
Nor do I need ISA-bus modems - or, in fact, ANY ISA bus components whatsoever. Nor Socket 7 motherboards. Or that extra Pentium Pro system. Or those 30-pin SIMMs.
You're getting the picture. I need to get rid of a lot of stuff.
The purges have begun, with the shipment (finally!) of almost 50 pounds of cards, cell phones, mice, cables, etc. to Dell as part of their recycling program.
The realization that I needed to get rid of this stuff happened long ago, but it was made more... temporally important... by virtue of the new house (and the need to move all of our stuff from our old place. I didn't want to just toss this stuff out with our regular trash, because isn't the right way to dispose of all the lovely lead, mercury, cadmium and other nasties that lurk within all this gear. In searching around, I stumbled onto Dell's Recycling page and ordered two of their "Consumer Recycling Kit with one airway bill" for US$10.
Over the next 22 months, I collected many cards, motherboards and other not-so-goodies and filled a box - finally ending up with 49 pounds and 14 ounces of electronic junk, and shipped it off this past week.
I had occasion to look around again, and realized that I needed to send more. I had given the other "Recycling Kit" to my similarly-afflicted friend Brad Schutter, so I figured I'd just order up a few more. Returning today to the link I found via Google today resulted in immediate disappointment, however, as I couldn't find any links to that which I'd previously ordered.
Fortunately, despite my tardiness in using them, my order was still within the 2-year window into your order history that Dell allows, so I found the original Dell part number (310-6492) - and lo and behold, I found the page with the actual item.
Take stock of the old electronics you (or your company) have in your posession, and consider this viable (and valuable) option for getting rid of the now-worthless electronic clutter that a) you no longer need to keep around, b) you can't sell on eBay for US$0.01, and c) has no value to charities like The National Cristina Foundation.
08 September 2007
Thnking of Verizon FiOS?
Here is something to consider before you make the jump to FTTH (Fiber To The Home) from Verizon:
Will you ever, in the future, require the use of the telecom copper cabling that currently feeds your house? I'm not talking about the telephone lines inside your walls, I'm referring to the copper pairs that come from your street.
Verizon's policy is that once you have FiOS installed, they will make unusable those pairs that go from their publicly-subsidized infrastructure to your home.
If you ever decide that you want to switch to a different telecom provider - one that would use those copper wires - you yould need have new lines run, at your cost (if Verizon would allow it at all).
The hidden agenda:
Verizon (and other ILECs (Incumbent Local Exchange Carriers) were required to provide open (low cost) access to their copper infrastructure to other CLECs (Competitive Local Exchange Carriers). This allowed companies other than the ILEC to provide DSL and other telecom services, without having to build out their own infrastructure.
Verizon lobbied hard to make sure that the same sort of access would not be required of them, were they to build out a new, fiber optic infrastrure. With that in place, they began to roll out FiOS to their territory.
The bottom line:
If you want the option to go with another telecom provider (for data or voice service) other than your cable company, get it in writing from Verizon that they will not destroy your existing copper infrastructure in any way.
Or, don't get FiOS at all.
Will you ever, in the future, require the use of the telecom copper cabling that currently feeds your house? I'm not talking about the telephone lines inside your walls, I'm referring to the copper pairs that come from your street.
Verizon's policy is that once you have FiOS installed, they will make unusable those pairs that go from their publicly-subsidized infrastructure to your home.
If you ever decide that you want to switch to a different telecom provider - one that would use those copper wires - you yould need have new lines run, at your cost (if Verizon would allow it at all).
The hidden agenda:
Verizon (and other ILECs (Incumbent Local Exchange Carriers) were required to provide open (low cost) access to their copper infrastructure to other CLECs (Competitive Local Exchange Carriers). This allowed companies other than the ILEC to provide DSL and other telecom services, without having to build out their own infrastructure.
Verizon lobbied hard to make sure that the same sort of access would not be required of them, were they to build out a new, fiber optic infrastrure. With that in place, they began to roll out FiOS to their territory.
The bottom line:
If you want the option to go with another telecom provider (for data or voice service) other than your cable company, get it in writing from Verizon that they will not destroy your existing copper infrastructure in any way.
Or, don't get FiOS at all.
Subscribe to:
Posts (Atom)