again a problem with tcpip and proxyarp

Franz Josef Pohlen

2006-02-24 10:27:19 UTC

Hi Alan,

the proxyarp problem is solved. Apar PK15521 (PTF UK09859) was the solution.
Now the host routes are put into the osa oat.

Franz Josef

> --- Ursprüngliche Nachricht ---
> Von: Franz Josef Pohlen <fjpohlen-***@gmx.de>
> An: VMESA-***@LISTSERV.UARK.EDU
> Betreff: Re: [VMESA-L] again a problem with tcpip and proxyarp
> Datum: Thu, 23 Feb 2006 09:05:00 +0100
>
> Hi Alan,
>
> thank you for your fast reply. As you suggested, I have opened a pmr with
> the number 94192-B033-C724 for the German customer Schumag AG.
>
> regards
> Franz Josef Pohlen
>
> > --- Ursprüngliche Nachricht ---
> > Von: Alan Altmark <***@us.ibm.com>
> > An: VMESA-***@LISTSERV.UARK.EDU
> > Betreff: Re: [VMESA-L] again a problem with tcpip and proxyarp
> > Datum: Wed, 22 Feb 2006 13:26:04 -0500
> >
> > On Wednesday, 02/22/2006 at 06:56 CET, Franz Josef Pohlen
> > <fjpohlen-***@gmx.de> wrote:
> >
> > > communication works ok between vse and zvm, but not to the outside
> > world.
> > > With osasf, I have seen, that the 10.0.0.132 is not known to the osa
> > device.
> > > I have expected to find this address in the dynamic oat entries. The
> vm
> > > addresses appear as expected. I attach the ip profile for vm and vse
> for
> > > documentation. I want to avoid, if possible, to define this nice
> > osa-express
> > > as CHP-Type OSE for connecting the vse directly. Hopefully someone can
> > help
> > > me to get it working.
> >
> > Miguel and I don't see anything wrong with your configuration. Go ahead
> > and call it in. Either PROXYARP isn't being recognized (check the
> console
> > log at initialization) or something is broken.
> >
> > Alan Altmark
> > z/VM Development
> > IBM Endicott
> >
>
> --
> Telefonieren Sie schon oder sparen Sie noch?
> NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie
>

--
Lust, ein paar Euro nebenbei zu verdienen? Ohne Kosten, ohne Risiko!
Satte Provisionen für GMX Partner: http://www.gmx.net/de/go/partner