Issues with Windows IP , LCS Hercules 3.312 , z/VM 5.3 TCPIP

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Issues with Windows IP , LCS Hercules 3.312 , z/VM 5.3 TCPIP

Hercules390 - Vm mailing list
I have CTCI-WIN Tuntap , Hercules 3.12 W64 , and z/VM 5.3 as guest.

 Host Win 7 64bit machine IP 192.168.2.17 , Gateway 192.168.2.1, IP routing disabled
tt64Test and tt32Test work pinging with default gateway 192.168.2.1,
 Ping to anything, or 192.168.2.17 Windows  works
 and from windows CMD  ping to TUNTAP guest ip 192.168.2.50 works
(windows)  Physical adapter MAC address 18-03-73-2A-81-A8 ,
(guest ) IP address 192.168.2.50 , Mac address 00-00-5E-A8-02-6F
 

 In Windows Properties for the adapter
Physical Address: 18-03-73-2A-81-A8
DHCP Enabled: Yes
IPv4 Address: 192.168.2.17
IPv4 Subnet Mask: 255.255.255.0
IPv4 Default Gateway: 192.168.2.1
IPv4 DHCP Server: 192.168.2.1
IPv4 DNS Server: 192.168.2.1
 and with Windows CMD I have added a persistent Route for IP
 Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
     192.168.2.50  255.255.255.255      192.168.2.1       1
 

 In Hercules I have
 0600-0601 LCS -n  <host>192.168.2.17 <guest>192.168.2.50
 

 

 *In VM config TCPIP PROFILE
 I do not have port 23 as I only want to use FTP to offload files from z/VM to windows
   ** note LINK ctclink1 CTC 1 (transmit side)
 PORT
 20 TCP FTPSERVE NOAUTOLOG ; FTP Server        
 21 TCP FTPSERVE ; FTP Server        
 111 TCP PORTMAP ; Portmap Server    
 111 UDP PORTMAP ; Portmap Server    
 DEVICE ctc0 CTC 0E40                  
LINK   ctclnk1 CTC 1 ctc0  MTU 9216
HOME                                                                    
  192.168.2.50   255.255.255.240 ctclnk1                                
GATEWAY                                                                
 192.168.2.17   HOST             =                    ctclnk1          0      
DEFAULTNET                       192.168.2.17   ctclnk1          0      
 START ctc0    

 *In VM ETC HOSTS file I have added
127.0.0.1     localhost loopback                    
192.168.2.17    MyWin7PC
 *In VM TCPIP DATA  (!!I do not have DNS server  starting! just using ip addrs)
DOMAINLOOKUP DNS
NSINTERADDR 192.168.2.1
NSPORTADDR 53
RESOLVEVIA UDP
 *In VM TCPIP
Profile EXEC
'Detach E40'      
'Detach E41'      
'Attach 600 * E40'
'Attach 601 * E41'
'Query 600-601'  
 Sometimes when Logging on  TCPIP user and running the start up process CTCA fails
 DTCCTC080I CTCA initializing:                        
DTCPRI385I  Device CTC0:                            
DTCPRI386I     Type: CTC, Status: Not started        
DTCPRI387I     Envelope queue size: 0                
DTCPRI388I     Address: 0E40                        
DTCPUP097I Precedence designations will be respected
DTCCTC083E CTCA device CTC0: Unexpected CSW from SenseId command on device E41                                                                        
DTCPRI461I    Keys: E0, CcwAddress: 00000008                          
DTCPRI462I    Status bits: C0, SCFA: 40C9                              
DTCPRI463I    Unit Status: 00, Channel Status: 80                      
DTCPRI464I    Byte Count:            0                                
DTCPRI470I    Subchannel Logout: 00800000                              
DTCPRI471I    Extended Report Word: 00000000                          
DTCCTC082E CTCA shutting down:                                        
DTCPRI385I    Device CTC0:                                            
DTCPRI386I       Type: CTC, Status: Sense ID on input                  
DTCPRI387I       Envelope queue size: 0                                
DTCPRI388I       Address: 0E40                                        

 In that case I shut down tcpip and ipl cms and start again ,
 

 *if CTCA doesn't fail get TCPIP console msgs looks like from TUNTAP??
 DTCCTC095E Sense id: FF 30 88 for device 0E41
 DTCCTC095E Sense id: FF 30 88 for device 0E40
 

  From TCPMAINT user cmd NETSTAT DEVLINKS

 Device CTC0                    Type: CTC            Status: Ready      
  Queue size: 0     CPU: 0     Address: 0E40                          
    Link CTCLNK1               Type: CTC            Net number: 1      
      BytesIn: 0               BytesOut: 0                            
      Forwarding: Enabled      MTU: 9216                              
      Broadcast Capability: Yes                                        
      Multicast Capability: Yes                                        
      Group                                   Members                  
      -----                                   -------                  
      224.0.0.1                                  1                    

 

 At this point I can not ping from guest machine to 192.168.2.17 host , nor can I ping from host Windows to Guest z/VM ! I can ping to 127.0.0.1 or 192.168.2.50 on guest vm fine. BytesIn and BytesOut seem to remain at 0 for CTC0.
 

 Please has anyone got any ideas? I really feel so close to getting FTP working...
 

 

 


 

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with Windows IP , LCS Hercules 3.312 , z/VM 5.3 TCPIP

Hercules390 - Vm mailing list
More information, my Windows route configuration follows:
 \===========================================================================
Interface List
 37........................... VPN
 11...18 03 73 2a 81 a8 ......Intel(R) 82579LM Gigabit Network Connection
  1...........................Software Loopback Interface 1
===========================================================================
IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
    0.0.0.0                 0.0.0.0                   192.168.2.1  192.168.2.17     20
   127.0.0.0              255.0.0.0               On-link         127.0.0.1    306
   127.0.0.1              255.255.255.255   On-link         127.0.0.1    306
   127.255.255.255  255.255.255.255   On-link         127.0.0.1    306
   192.168.2.0          255.255.255.0       On-link         192.168.2.17    276
   192.168.2.17        255.255.255.255   On-link         192.168.2.17    276
   192.168.2.50        255.255.255.255   192.168.2.1 192.168.2.17     21
   192.168.2.255      255.255.255.255   On-link         192.168.2.17    276
   192.168.56.0        255.255.255.0       On-link         192.168.56.1    276
   192.168.56.1        255.255.255.255   On-link         192.168.56.1    276
   192.168.56.255    255.255.255.255   On-link         192.168.56.1    276
        224.0.0.0        240.0.0.0                On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0               On-link          192.168.56.1    276
        224.0.0.0        240.0.0.0               On-link          192.168.2.17    276
  255.255.255.255  255.255.255.255   On-link          127.0.0.1    306
  255.255.255.255  255.255.255.255   On-link          192.168.56.1    276
  255.255.255.255  255.255.255.255   On-link          192.168.2.17    276
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
     192.168.2.50  255.255.255.255      192.168.2.1       1


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

RE: Issues with Windows IP , LCS Hercules 3.312 , z/VM 5.3 TCPIP

Hercules390 - Vm mailing list
In reply to this post by Hercules390 - Vm mailing list
Someone who did not tell us their name said:

[...]
> In Windows Properties for the adapter
> Physical Address: 18-03-73-2A-81-A8
> DHCP Enabled: Yes
> IPv4 Address: 192.168.2.17
> IPv4 Subnet Mask: 255.255.255.0

Okay.


> IPv4 Default Gateway: 192.168.2.1

Okay.


> IPv4 DHCP Server: 192.168.2.1
> IPv4 DNS Server: 192.168.2.1
>
> and with Windows CMD I have added a persistent Route for IP
>
> Persistent Routes:
>   Network Address          Netmask  Gateway Address  Metric
>      192.168.2.50  255.255.255.255      192.168.2.1       1

Why?


> In Hercules I have
>  0600-0601 LCS -n  <host>192.168.2.17 <guest>192.168.2.50

Okay.



[...]
> DEVICE ctc0 CTC 0E40
> LINK   ctclnk1 CTC 1 ctc0  MTU 9216

Wrong.

1. A "CTC" device is not the same as an "LCS" device.  They are two completely different animals.  You told Hercules to emulate an LCS device.  Why would you then tell z/VM that is was a CTC device?  You need to define an LCS DEVICE and LINK here, not CTC.

2. Your specified MTU is *way* too large.  CTCI-WIN does not support jumbo frames.  Try using 1492 or smaller.



> HOME
>   192.168.2.50   255.255.255.240 ctclnk1

Wrong.

1. The Windows adapter you are using has 255.255.255.0 defined for its subnet mask.  Your Hercules guest should specify the same value.

2. Your link name (ctclnk1) will need to be adjusted once you fix your DEVICE and LINK statements (see previous).



> GATEWAY
>  192.168.2.17   HOST             =                    ctclnk1

Wrong.

1. 192.168.2.17 is NOT your gateway.  The Windows adapter you are using has 192.168.2.1 defined as its default gateway.  Your Hercules guest should specify the same value.

2. Your link name (ctclnk1) will need to be adjusted once you fix your DEVICE and LINK statements (see previous).



> 0
> DEFAULTNET                       192.168.2.17   ctclnk1          0

Wrong.


1. 192.168.2.17 is NOT your gateway.  The Windows adapter you are using has 192.168.2.1 defined as its default gateway.  Your Hercules guest should specify the same value.

2. Your link name (ctclnk1) will need to be adjusted once you fix your DEVICE and LINK statements (see previous).


>  START ctc0

Wrong.

1. Your device name (ctc0) will need to be adjusted once you fix your DEVICE and LINK statements (see earlier).


Please read the Help file that came with the product.  It's there to help you.

--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: [hidden email]




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with Windows IP , LCS Hercules 3.312 , z/VM 5.3 TCPIP

Hercules390 - Vm mailing list
In reply to this post by Hercules390 - Vm mailing list
[...]
> Persistent Routes:
>   Network Address          Netmask  Gateway Address  Metric
>      192.168.2.50  255.255.255.255      192.168.2.1       1

WHY?

--
"Fish" (David B. Trout)
Software Development Laboratories
http://www.softdevlabs.com
mail: [hidden email]




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with Windows IP , LCS Hercules 3.312 , z/VM 5.3 TCPIP

Hercules390 - Vm mailing list
In reply to this post by Hercules390 - Vm mailing list
Great, Thanks for the info.
 Re gateway I thought from some details you had posted that Gateway through TUNTAP works using the win Host PC IP not the actual Gateway on the router.  Thanks! Maybe because I confused description of  the MAC addr of the TUNTAP description or something. (I have been using VPN forever too, and maybe confused with VPN , TUNTAP, route, gateways  etc...)
 Also along the way I had tried LCS device in VM  and in Herc parms but always came up offline, assumed misunderstood and that all TUNTAP devices appear as CTCA in VM so defined as CTC In TCPIP parms, I guess LCS may appear as CTCA but the PAMS have to describe as LCS not CTC .
 

 Thanks for the help Fish.
 Will give all this a fix up and re-test.
 

 Greycoder
 

 

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Issues with Windows IP , LCS Hercules 3.312 , z/VM 5.3 TCPIP

Hercules390 - Vm mailing list
In reply to this post by Hercules390 - Vm mailing list


 guest IP 192.168.2.111
 host ip 192.168.2.17  
 gateway 192.168.2.1
 no windows route to guest IP,
 

 On z/VM PROFILE TCPIP
     DEVICE lcs0  LCS 0E40                
    LINK   lcslnk0 ETHERNET 0 lcs0 MTU 1492  

 HOME                                      
  192.168.2.111  255.255.255.0   lcslnk0  
GATEWAY                                                              
  192.168.2.1    HOST            =                     lcslnk0     0
   224.0.0.0       255.255.255.0 192.168.2.1   lcslnk0     0  
DEFAULTNET                       192.168.2.1    lcslnk0     0
 

 Start TCPIP (Does not auto start links)
 Logon TCPMaint user to start tcpip and then link
 autolog tcpip tcpip
 NETSTAT OBEY START lcs0
 

 It works !!! THANK YOU "Fish" !!
 I can ping my windows host from guest, and ping guest from Windows                                        
 

 Now have to see if I can get an FTP client on windows connecting & downloading from z/VM , so more fun..  ;-) .
 Very , very much appreciate the help.
 Thanks!
 Greycoder.

Loading...