The biggest value for us has been:
Being able to run several workloads that require a separate machine for SQL
Server type apps but only get run once a month (security scanning, backup
surf control, etc.). We can easily leave these types of niche servers down
all month and then bring them all up as needed on a single hardware IXS
card.
Using a server to test between multiple SW packages or versions is a breeze
when you can save/restore/detach/attach different storage spaces or server
configs. This made the evaluation of several software packages much less
work, but still let us switch between them as needed (it never would have
got evaluated as fully without being able to use that IXS functionality).
The are great for niche type servers that don't need quite as much
horsepower, but it would definitely be tough to get ALL the Windows boxes
most shops need under the IXS based covers (so to speak). The dependencies
that can occur when switching between 2 HA servers once a month that also
house our IXS cards also would make it tough to bring in other servers to
that model.
We are still big fans of them and will stick with at least a few of them at
least through our next gen of iSeries (not interested in the blade model
until we have to go that way).
"Lukas Beeler"
<l.beeler@datalin
e.ch> To
Sent by: "Midrange Systems Technical
midrange-l-bounce Discussion"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
04/02/2007 03:26 Subject
PM RE: Windows Integration and
Longhorn
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
The problem with the Storage Space thingy you're proposing is that this
will have consequences if you're running a DC on that machine.
Read this:
http://support.microsoft.com/kb/875495
I don't see how IXS help to save cost on the software side - you will
still need competent windows administrators, and they will still have to
do the same job.
The HW maintenance thing sounds logical at first, but when you have to
size up your System I to be a full blown SAN for all your windows needs,
you will need so many expansion towers that you might be in similar
waters - though the System I might still be cheaper.
When we're talking IXA or iSCSI attachment, you will only have a SAN
left. You will still have to pay for HW maintenance.
Also, I find it embarrassing for IBM that a 5000CHF PC-on-a-Card doesn't
have remote KVM.
I really fail to see the advantages of IXS/IXA as long as they are more
than twice as expensive as a fully loaded System x.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jones, John (US)
Sent: Monday, April 02, 2007 9:10 PM
To: Midrange Systems Technical Discussion
Subject: RE: Windows Integration and Longhorn
Vary off Network Server (NWS). Copy Storage Space to backup. Vary on
NWS. After all, you should back up before installing a service pack or
other major app/OS update. Moving on ..
Load Service Pack. SP Fails? Vary off, revert to copy, vary on, do
diagnostics later if on-site required. Optionally, and this is neat,
add the storage space to your NWS as drive D: or whatever and look at
the files from the working NSW. Or boot it to your backup IXS (which
could be in another machine/data center).
The reason we use them? Cost. Server administration is outsourced and
we pay for each physical server. IXS costs $0 to admin over and above
the iSeries admin costs. Also, $0 hardware maintenance costs. Also,
better quality maintenance that PC server providers (I could mention the
YEARS we waited for Dell to replace a failed disk in a RAID set). Also,
with over 200 Windows servers in a single data center, the
zero-footprint IXS helps manage space in the data center. Also, it uses
little power (22 watt PentiumM + some for the rest of the card) over and
above what is used anyway for the iSeries. That corresponds to very
little waste heat as well.
Finally, if you really need it you can get a KVM switch that allows for
remote access, for instance:
http://www.minicom.com/kvm_smart16ip.htm
--
John A. Jones, CISSP
Americas Information Security Officer
Jones Lang LaSalle, Inc.
V: +1-630-455-2787 F: +1-312-601-1782
john.jones@xxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lukas Beeler
Sent: Monday, April 02, 2007 1:54 PM
To: Midrange Systems Technical Discussion
Subject: RE: Windows Integration and Longhorn
And IXS don't have that?
Seems that this isn't really such a great solution...
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Larry Bolhuis
Sent: Monday, April 02, 2007 8:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Windows Integration and Longhorn
With most iSCSI and IXA attached 'x' the RSA II Is installed so you have
the option to use that if you need it.
- Larry
Lukas Beeler wrote:
Hi John,
I meant the tools used when the OS doesn't boot, for some reason (i.e.
a
failed service pack install, failed upgrade, or similar mishap).
How do I access the system console in such a case? Do I have to go
local? Or do I have some sort of remote access, like the RSA II used
for
"normal" IBM servers?
How do I boot and use the system in Directory Services Recovery mode?
(On an Active Directory Domain ControlleR).
All these thing need access to the system, before the TCP/IP stack is
loaded.
-
--
Larry Bolhuis IBM eServer Certified Systems Expert:
Vice President iSeries Technical Solutions V5R3
Arbor Solutions, Inc. iSeries LPAR Technical Solutions V5R3
1345 Monroe NW Suite 259 iSeries Linux Technical Solutions V5R3
Grand Rapids, MI 49505 iSeries Windows Integration Technical
Solutions V5R3
IBM eServer Certified Systems Specialist
(616) 451-2500 iSeries System Administrator for
OS/400 V5R3
(616) 451-2571 - Fax AS/400 RPG IV Developer
(616) 260-4746 - Cell iSeries System Command Operations V5R2
If you can read this, thank a teacher....and since it's in English,
thank a soldier.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
This email is for the use of the intended recipient(s) only. If you
have received this email in error, please notify the sender immediately
and then delete it. If you are not the intended recipient, you must not
keep, use, disclose, copy or distribute this email without the author's
prior permission. We have taken precautions to minimize the risk of
transmitting software viruses, but we advise you to carry out your own
virus checks on any attachment to this message. We cannot accept
liability for any loss or damage caused by software viruses. The
information contained in this communication may be confidential and may
be subject to the attorney-client privilege. If you are the intended
recipient and you do not wish to receive similar electronic messages
from us in the future then please respond to the sender to this effect.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at
http://archive.midrange.com/midrange-l.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit
http://www.ers.ibm.com
_____________________________________________________________________________
ForwardSourceID:NT00068C3E
midrange.com
