Pictures and email....arrg!
________________________________________________________________
| | |
| lpar0 | lpar1 |
| z/VM 5.1 (390) | z/VM 5.1 (IFL) |
| cua 2000-2002 OSA | cua 2010-2012 OSA |
| 205.235.227.74 home | 192.168.193.3 home |
| netmask 255.255.255.0 | netmask 255.255.252.0 |
| gateway 205.235.227.41 | gateway 192.168.192.1 |
_________________________________________________________________
| Guest Machines (VSE) | Guest machines zLinux |
| 192.168.99.xxx | 192.168.193.xxx |
| using vswitch | using vswitch |
_________________________________________________________________
| VMTEST z/VM 5.2 |
| cua 2016-2018 |
| 192.168.194.4 home |
| netmask 255.255.255.0 |
| gateway 192.168.194.1 |
_________________________________
On the VMTEST system, I don't care what IP address it is. Nor do I
care about the netmask or gateway. I was attempting to use some of the
unused addresses in my supernet.
A little history. When the z/890 was being installed, I asked the
network guys for 4 ranges of addresses.
1 set for the IFL side
1 set for the internal lan on the z/890 (between the laptops and Win/XP
remote service console)
1 set for our new DS6800 (between the laptops and the Win/XP remote
service console)
1 set for the 390 side (for use while we had our 205.235.227.74 network
on the MP3000, I needed another set on the z/890 390 side for parallel
testing)
Instead of 4 separate networks that didn't interfer with each other,
they gave me 4 class C networks bundled together as a supernet. I sure
didn't need 1000+ IP addresses, but they gave them to me and they
worked. So far. I didn't use any of them for the z/890 or for the
DS6800. By time they configured the supernet, I had some other
addresses for these boxes.
Now, for the first time, I'm trying to use some of these "extra" ip
addresses. I thought that the IFL side, that has the supernet, might be
intefering with my "other" use of some addresses in the VMTEST machine.
But I took down LPAR1 with the supernet and brought up VMTEST as a
first level system in LPAR1. I still couldn't connect. So this implies
to me that I don't have a problem, yet, with the supernet stuff.
OK I see what you mean about the defaultnet. I changed my statements
to:
HOME
192.168.194.4 255.255.255.000 QDIO1
; (End HOME Address information)
;
----------------------------------------------------------------------
|...+....1....+....2....+....3....+....4....+....5....+....6....+....7....+..
GATEWAY
; Network Subnet First Link MTU
; Address Mask Hop Name Size
; ------------- --------------- --------------- ---------------- -----
205.235.227 255.255.255.0 = QDIO1 1500
DEFAULTNET 192.168.194.1 QDIO1 1500
; DEFAULTNET 205.235.227.41 QDIO1 1500
; (End GATEWAY Static Routing information)
;
----------------------------------------------------------------------
It didn't seem to make any change....
netstat gate
VM TCP/IP Netstat Level 520
Known IPv4 gateways:
Subnet Address Subnet Mask FirstHop Flgs PktSz Metric Link
-------------- ----------- -------- ---- ----- ------
------
Default <none> 192.168.194.1 UGS 1500 <none>
QDIO1
192.168.194.0 255.255.255.0 <direct> UT 1500 <none>
QDIO1
205.235.227.0 255.255.255.0 <direct> US 1500 <none>
QDIO1
Known IPv6 gateways: None
Ready; T=0.02/0.03 13:40:21
ping 192.168.194.1
Ping Level 520: Pinging host 192.168.194.1.
Enter 'HX' followed by 'BEGIN' to interrupt.
PING: Ping #1 timed out
Ready(00004); T=0.05/0.06 13:40:43
ping 205.235.227.41
Ping Level 520: Pinging host 205.235.227.41.
Enter 'HX' followed by 'BEGIN' to interrupt.
PING: Ping #1 timed out
Ready(00004); T=0.05/0.06 13:40:54
I keep thinking that there may be something about the ports, the
addresses (2016-2018) that need to be activated or something.
First level (LPAR0):
q osa
OSA 2000 ATTACHED TO VSWCTRL1 2000
OSA 2001 ATTACHED TO VSWCTRL1 2001
OSA 2002 ATTACHED TO VSWCTRL1 2002
OSA 2003 ATTACHED TO VSWCTRL1 2003
OSA 2004 ATTACHED TO VSWCTRL1 2004
OSA 2005 ATTACHED TO VSWCTRL1 2005
OSA 2016 ATTACHED TO VMTEST 2016
OSA 2017 ATTACHED TO VMTEST 2017
OSA 2018 ATTACHED TO VMTEST 2018
OSA 2200 ATTACHED TO VMTEST 2200
OSA 2201 ATTACHED TO VMTEST 2201
OSA 2202 ATTACHED TO VMTEST 2202
OSA 2203 ATTACHED TO VMTEST 2203
OSA 2204 ATTACHED TO VMTEST 2204
OSA 2205 ATTACHED TO VMTEST 2205
MAINT ZVMV5R10 12/04/2006; T=0.01/0.01 12:42:37
Second level (VMTEST):
q osa
OSA 2016 ATTACHED TO TCPIP 2016 DEVTYPE OSA CHPID 11 OSD
OSA 2017 ATTACHED TO TCPIP 2017 DEVTYPE OSA CHPID 11 OSD
OSA 2018 ATTACHED TO TCPIP 2018 DEVTYPE OSA CHPID 11 OSD
Ready; T=0.01/0.01 13:42:25
No matter what change I make, it doesn't seem to make a difference. So
I know that I'm looking in the wrong area to make changes to. Once I
find the right thing to change, I have a lot of work with the CONFIG
file, to get things back to what I wanted in the first place. (Which
was to be able to FTP from first level to second level so I can copy
files over that I need, without staging thru minidisks or tape.)
Thanks for the help
Tom Duerbusch
THD Consulting
>>> [EMAIL PROTECTED] 12/5/2006 11:50 AM >>>
The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> wrote on
12/05/2006 09:35:52 AM:
> 1. 192.168.194.1 isn't a host. I was under the impression that,
> 192.168.194.1 is the default gateway for a router. Of course, I'm
> usually wrong in the IP world<G>.
Well, as long as 192.168.194.1 is up and actually connected to the same
network as your node, you should be able to PING it. Could you put
together a rough diagram of your network?
> 2. Based on z/VM 5.1 on LPAR1, I should be able to ping the
> 205.235.227.xx addresses.
> The CONFIG file for LPAR1 has:
> GATEWAY
>
> ; Network First Link MTU Subnet
> Subnet
> ; Address Hop Name Size Mask
> Value
> ; ------------- --------------- ---------------- -----
---------------
> --------
> 192.168.192 = QDIO1 1500 000.000.003.0
> 0
> DEFAULTNET 192.168.192.1 QDIO1 1500 0
>
> ; (End GATEWAY Static Routing information)
>
> ;
>
----------------------------------------------------------------------
>
> START [EMAIL PROTECTED]
>
> ; (End START statements)
>
The 5.1 system is able to PING 205.235.227.xx addresses via the
DEFAULTNET
statement above. In the NETSTAT GATE output for your 5.2 system you
had:
Default <none> 205.235.227.41 UGS 1500 <none>
QDIO1
205.235.227.0 255.255.255.0 <direct> US 1500 <none>
QDIO1
The second line implies you are directly connected to the
205.235.227.0/24
network which, based on your IP address, is not true.
Regards,
Miguel Delapaz
z/VM TCP/IP Development
