Hi guys,
Any appliance firmware is nothing but a shell install
script coupled with a tar archive carrying code. The code
itself is a Java application.
You need to install a fresh CentOS 5 (Linux) x86 operating
system onto a VM. Upload a "firmware" file, make
executable, and just run. Don't forget to reboot after to
reset LD_LIBRARY_PATH. When the Java code (location
management application) starts, it looks for certain
hardware parameters via dmidecode utility. You have to
play around to make it "happy".
Any further public disclosure of internals is known as
hacking, which violates certain Cisco copyrights and
intellectual property. I am not comfortable putting my
number at risk, sorry.
Regards,
Anton Vinokurov
CCIE #23134 (R&S), CCDP
[email protected]
On Mon, 20 Dec 2010 10:57:15 -0500
Jason Boyers <[email protected]> wrote:
I would be interested in seeing that as well.
Everything I've seen and
tried gave the impression that it could not be done. If
it can (without the
special build Dominic mentioned), we're all ears.
Jason Boyers - CCIE #26024 (Wireless)
Technical Instructor - IPexpert, Inc.
Mailto: *[email protected]
*
On Mon, Dec 20, 2010 at 10:21 AM, Yuri Mecca
<[email protected]> wrote:
Hi Anton,
Could you provide the step by step or any guide to
virtualize the Location
Appliance? I try a couple of months but this don't work.
Best Regards,
Yuri
------------------------------
From: [email protected]
To: [email protected];
[email protected]
Date: Mon, 20 Dec 2010 18:17:03 +0300
Subject: Re: [CCIE Wireless] CCIE_Wireless Digest, Vol
21, Issue 10
Hi All,
2710 Location Appliance virtualization is trivial.
3310/3350 Mobility Services Engine virtualization is a
bit more
complicated, but also straightforward.
Obviously you need to have a WCS with Location (Plus)
license, otherwise
your Location engines are pretty useless.
All other stuff like DNS, Windows domain (AD), CA, ACS
(including 5.0), WCS
can be easily virtualized as well.
Virtualized hardware runs in production environment even
better than native
appliance-based one. You get HA, DRS, increased
manageability, scalability
and other nice features. Of course, not officially
supported.
2106 controller (its hardware is the same as for
ASA5505) is theoretically
possible to virtualize as well. I gave up after few
weeks trying J From
the practical standpoint, it may take months as one have
to write a
MontaVista 4 Linux driver for Marvel 88E60xx chip J If
you have a spare
ASA box, I guess it is possible to “convert” it to 2106.
It is likely NOT possible to run higher controller (440x
and 5508) code in
virtual environment as CPU architecture is not i386
(440x is ARM, and 5508
is MIPS64).
Regards,
Anton Vinokurov
CCIE #23134 (R&S), CCDP
[email protected]
*From:* [email protected]
[mailto:
[email protected]] *On Behalf Of
*Geek Mega
*Sent:* Monday, December 20, 2010 4:54 PM
*To:* [email protected]
*Subject:* Re: [CCIE Wireless] CCIE_Wireless Digest, Vol
21, Issue 10
Has anyone managed (or trying) to get WLC working on VM?
Does anyone know how to extract BiOS from wlc2106 (if it
is possible at
all) or where to get one from?
ZZZ
_______________________________________________ For more
information
regarding industry leading CCIE Lab training, please
visit
www.ipexpert.com
_______________________________________________
For more information regarding industry leading CCIE Lab
training, please
visit www.ipexpert.com
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
