Sorry to post and run, but here's the scoop so that you have it.
Just a reminder that the first 2008 Live Virtual Class is on
set for Monday, March 3rd at 11:00 AM ET.
There is no charge to participate in this technical education session.
Date: Monday, March 3, 2008
Time: 11:00 AM ET / 4:00 P
> O> I'd argue that you will have more problems trying to make this work
> > reliably than just doing it the way I described. If you've got time
to
> > debug this and all the paths have equivalent permissions and
usability
> > characteristics, then yes, it's technically possible. You just have
to
>
O> I'd argue that you will have more problems trying to make this work
> reliably than just doing it the way I described. If you've got time to
> debug this and all the paths have equivalent permissions and usability
> characteristics, then yes, it's technically possible. You just have to
> have a
Many thanks to Mark Post, John Summerfield, Adam Thornton and especially
Piotr Kolasinski for all the time and effort they put into getting my system
up and running.
I hope that one day I will know enough about the system to be able to "pay
it forward".
Regards,
D.J. Foreman, Ph.D.
website: http:
> You don't have to have a per interface IP address or DNS (or indeed
MAC
> address), but they must be at least per host (and virtual machines
with
> their own IP stack are a host). IP is quite happy with that situation.
I'd argue that you will have more problems trying to make this work
reliably
>>> On 2/28/2008 at 8:57 AM, in message
<[EMAIL PROTECTED]>, David
Boyes <[EMAIL PROTECTED]> wrote:
>> When setting up the IP address for a hipersocket I am curious as to if
>> people are giving it the same IP address as with the regular outside
> of
>> the mainframe (OSA or whatever) IP address.
Problem solved. The original .config file (which I used as a base) did not
have the DASD or TTY drivers & devices built into the kernel, but had them
set to be loaded in as modules, which didn't happen when I tried to run my
build. I re-did the build, specifying that they have to be built-in and i
> Absolutely DO NOT do this. Each interface needs a unique address (and
> IMHO, a unique DNS name). The whole premise of IP routing and network
> function is based on this concept.
You don't have to have a per interface IP address or DNS (or indeed MAC
address), but they must be at least per host
> When setting up the IP address for a hipersocket I am curious as to if
> people are giving it the same IP address as with the regular outside
of
> the mainframe (OSA or whatever) IP address.
Absolutely DO NOT do this. Each interface needs a unique address (and
IMHO, a unique DNS name). The whol
On Wed, Feb 27, 2008 at 06:55:09PM -0800, Ted Rodriguez-Bell wrote:
> I'm trying to set up a connection to a SAN device with NPIV on. This
> works with NPIV off. When we turn NPIV on, VM seems to see it:
> tc-db2-sles9x-02# hcp q fc42
> FCP FC42 ON FCP FC42 CHPID F1 SUBCHANNEL = 0001
>
On Mon, Feb 11, 2008 at 10:42:57PM +0100, MAYER Andreas wrote:
> Since hwdown and hwup is not useable (at least for me) because SCSI host
> adapter is not removed anymore I followed the suggestion to configure
> the tape devices using a script.
> We don't use multipathing for tape devices, is ther
11 matches
Mail list logo
