Re: TCPIP config changes in z/VM 5.2
Hello Miguel, Indeed, this ptf will fix the NETSTAT GATE display. The default is now shown as UGS. The NETSTAT GATE now shows the same output on both the old and new VM. Well, besides the fact that the display itself does show the records a bit differently. But it didn't solve my orginal problem, I still can't ping some machines. So I guess there is something missing or in error in the new configs. Regards, Berry.
Re: TCPIP config changes in z/VM 5.2
Berry, This issue was addressed in APAR PK42210 Regards, Miguel Delapaz z/VM TCP/IP Development > Now I noticed the default was presented as a default gateway (flags UGS) > in the old VM and the new one is a host (flags UGHS). Other than that I > think the netstat gate output is the same in both systems. > > Any ideas on how to fix this? > > TIA, Berry.
TCPIP config changes in z/VM 5.2
Hello List, Last Friday we migrated one of our VM systems. This VM is one of four tha t use static routing only. Now I have found that the IP configuration rules have been changed in z/VM 5.2. So I changed the HOME and GATEWAY statements in the configuration file. Unfortunatly I haven't been able to get it fully functional. I can ping my gateway and even the nameserver bu t I can't ping the servers I need to access. The old z/VM 4.4 configuration: HOME 10.81.32.11 CTCLVM42 10.81.32.11 CTCLVM43 10.81.32.11 CTCLVM45 10.81.32.11 OSAETH2 10.81.32.01 OSAETH0 GATEWAY ; (IP) Network FirstLink Max. Packet Subnet Subnet ; Address Hop Name Size (MTU) MaskValue ; --- --- --- --- ; 10.81.32.13 =CTCLVM42 1500 HOST 10.81.32.15 =CTCLVM45 1500 HOST 10.81.32.17 =CTCLVM43 1500 HOST 10=OSAETH2 1500 0.255.255.0 0.81.32. 0 DEFAULTNET10.81.32.253 OSAETH2 1500 0 A NETSTAT GATE will present me with: Default 10.81.32.253 UGS 1500 OSAETH2 10.0.0.0 US 1500 0.255.255.0 0.81.32.0 OSAETH2 10.81.32.13 UHS 1500 HOST CTCLVM42 10.81.32.15 UHS 1500 HOST CTCLVM45 10.81.32.17 UHS 1500 HOST CTCLVM43 Now the new VM (actually a diffent node but the same idea): HOME 10.81.32.17 CTCLVM32 10.81.32.17 CTCLVM34 10.81.32.17 CTCLVM35 10.81.32.17 255.255.255.0 OSAETH2 10.81.32.07 OSAETH0 GATEWAY 10.81.32.11 HOST =CTCLVM34 1500 10.81.32.13 HOST =CTCLVM32 1500 10.81.32.15 HOST =CTCLVM35 1500 DEFAULTNET10.81.32.253 OSAETH2 1500 A NETSTAT GATE will show: Subnet Address Subnet Mask FirstHopFlgs PktSz Metric Link -- --- - -- -- Default HOST 10.81.32.253UGHS 1500 OSAETH 2 10.81.32.0 255.255.255.0UT 1500 OSAETH 2 10.81.32.11 HOST UHS 1500 CTCLVM 34 10.81.32.13 HOST UHS 1500 CTCLVM 32 10.81.32.15 HOST UHS 1500 CTCLVM 35 When I check the connections I try: PING 10.81.32.11 (this will ping through a CTC connection) PING 10.81.32.253 (this is the gateway) PING 10.1.1.25 (this is our nameserver as specified in the TCPIP DATA) PING 10.1.1.73 (this is a NT server but can't be pinged in the new VM). When I try to ping the server by its name (PING HNYM-CDT1) the name get's resolved and the ping will try to reach 10.1.1.73, but no success. Now I noticed the default was presented as a default gateway (flags UGS) in the old VM and the new one is a host (flags UGHS). Other than that I think the netstat gate output is the same in both systems. Any ideas on how to fix this? TIA, Berry.
