I'm in the mist of converting from z/VM 5.1 to z/VM 5.2 and having an IP
problem.
The VM stack is connected to a vswitch. And as far as the VM side is
concerned, all is well, (FTP, PING, TN3270, etc).
My, more modern VSE guests (2.5 and above) are connected to the vswitch
and all seems to be well.
However, my old VSE systems (2.3) are VCTCA routed thru z/VM and I have
no connection what so ever.
I know what the problem is, it is me. <G>
Actually, I couldn't just take my ZVMV5R10 TCPIP statements and put
them on the newer system. I had to rewrite many of them.
The only test systems I had to test with when I was testing z/VM 5.2
second level were newer VSE systems connected via vswitch.
>From VSE (TCP/IP 1.5B) I get:
0016: IPL395E Senseid I/O error on receive port, Cuu:0982 Sns:40
LinkID: LINK02
0016: IPL391E Unable to Initialize CTC Adapter, Cuu:0982 Linkid:
LINK02
They are coupled:
AR 0015 CTCA 0982 3088 COUPLED TO TCPIP 0923 SUBCHANNEL = 0003
AR 0015 CTCA 0983 3088 COUPLED TO TCPIP 0922 SUBCHANNEL = 0004
I have Sunday and Monday to straighten out this problem before I back
out. I'm toying with the idea of running the old z/VM 5.1 stack on z/VM
5.2.
I can't ping from VM to VSE.
I can't ping from VSE to VM.
Pieces of the VM config file:
; The following configuration is for St. Louis City Hall - NEWESA4
DEVICE NEWESA4 CTC 0922
LINK LNEWESA4 CTC 0 NEWESA4
HOME
205.235.227.74 255.255.255.000 QDIO1
; (End HOME Address information)
;
----------------------------------------------------------------------
;
----------------------------------------------------------------------
; Primary interface Definition
;
----------------------------------------------------------------------
PRIMARYINTERFACE QDIO1
;
----------------------------------------------------------------------
GATEWAY
; Network Subnet First Link MTU
; Address Mask Hop Name Size
; ------------- --------------- --------------- ---------------- -----
205.235.227 255.255.255.0 = QDIO1 1500
192.168.099.24 HOST = LNEWESA4 1500
DEFAULTNET 205.235.227.41 QDIO1 1500
; (End GATEWAY Static Routing information)
START NEWESA4
With the VM startup, I got the same errors I've normally had. Of
course, they may be more serious now.
15:03:21 DTCPAR123I LINE 231: NO IPV4 HOME ADDRESS FOR DEVICE NEWESA4
15:03:21 DTCPDO069I ADDBSDINFO: NO IPV4 HOME ADDRESS FOR LINK LNEWESA4
15:03:21 DTCPAR106I DEVICE:NEWESA4, TYPE:CTC
15:03:21 DTCPAR107I LINK: LNEWESA4, TYPE: CTC, NETWORK NUMBER: 0
15:03:21 DTCPDO076I 192.168.99.24 <DIRECT> LINK NAME: LNEWESA4
NAME: NEWESA4, DEV TYPE: CTC MAX 1500
HOST ROUTE
Obviously, I'm at a loss right now.
Thanks
Tom Duerbusch
THD Consulting
