RE: SNA usage and ObjectConnect

OK, I'll sketch this out quickly.

Two LPARS named SYSTEMA and SYSTEMB, LCPs are also SYSTEMA and SYSTEMB.

Network DNS says that systema and systema.mycompany.com is at
172.16.19.23 and systemb and systemb.mycompany.com is at 172.16.19.24.

But Anynet over the VLAN uses your local host table, which says that
SYSTEMA and SYSTEMA.APPN.SNA.IBM.COM is at 192.168.9.11 and SYSTEMB and
SYSTEMB.APPN.SNA.IBM.COM is at 192.168.9.12.

ObjectConnect over the VLAN will work fine. Most internal users won't
have any problems. But you *might* have some intermittent problems
transferring files or running commands using iNav, because iNav/MGTC
will expect the host table and DNS to agree where SYSTEMA and SYSTEMB
are.

This can be avoided if the DNS name is different than the System/LCP
name.

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Midwest Region Data Center
Fiserv.


-----Original Message-----
From: Evan Harris [mailto:spanner@xxxxxxxxxx]
Sent: Tuesday, April 14, 2009 6:25 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SNA usage and ObjectConnect

Hi Scott

I don't see a problem using a hosts table for these links as no other
systems would need to know the internal vlan addresses in any scenario I
can think of.

Also I can think of a couple of situations where I might want to do this
without being connected to the network - and hence no access to the DNS
server

Regards
Evan Harris


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ingvaldson, Scott
Sent: Wednesday, 15 April 2009 9:24 a.m.
To: Midrange Systems Technical Discussion
Subject: RE: SNA usage and ObjectConnect

Absolutely, works like a charm. You do need to take your network naming
standards into consideration. It gets tricky if you already use your
LPAR system names in the DNS and then try to use the same names for
AnyNet on the VE.

Regards,

Scott Ingvaldson
Senior IBM Support Specialist
Midwest Region Data Center
Fiserv.