I cannot get my VM TCPIP running on my t-server

Discussion:

(too old to reply)

Pohlen (Mailinglist)

2006-02-15 16:15:49 UTC

cross posted to VM list and Flex-ES list

Hi all,

I have had big trouble with my ethernet adapters on my t-server. They were all unusable, but now they are running again. I have started zVM and can use the emulated non-SNA devices over my LAN. The only thing which doesn't work up to now, is the tcpip network connection from the zVM, which was surely ok before the error. FLEX-ES starts with no error with all control units available but if I start the Ethernet interface in zVM TCPIP (/dev/net2), flex-es produces an alert with the following message:

FSINA100 2006/02/15 09:03:04 ENETDEV: ALERT trace dump taken for device 0e20 (tserver01:/var/adm/flexes/tserver1/devtr.2036.0)

On TCPIP startup appears the following message

16:19:17 DTCPKT047I Device LCS1: Received startup packet
16:19:18 DTCPKT105E Device LCS1: No control packet received in response to Start
Lan command
16:19:18 DTCPC3082E PCCA3 shutting down:
16:19:18 DTCPRI385I Device LCS1:
16:19:18 DTCPRI386I Type: LCS, Status: Ready
16:19:18 DTCPRI387I Envelope queue size: 0
16:19:18 DTCPRI388I Address: 0E20

20.2.350 DTCPKT105E

__________________________________________________________________________
DTCPKT105E Device devicename: No control packet received in response to
Start Lan Command

Explanation: The indicated device did not return a control packet in response to the Start Lan control command.

System Action: The device is shutdown, although TCP/IP continues.

User or Operator Response: See the operator's manual for the device to determine the troubleshooting procedure..

System Programmer Response: Assist the user as necessary.

The VM-TCPIP device appears as follows

q ctc
CTCA 0E20 ATTACHED TO TCPIP 0E20
CTCA 0E21 ATTACHED TO TCPIP 0E21
Ready; T=0.01/0.01 16:26:04

----------------------------------------------------------

netstat de
VM TCP/IP Netstat Level 510

Device LCS1 Type: LCS Status: Inactive
Queue size: 0 CPU: 0 Address: 0E20
Link ETH1 Type: ETHERNET Net number: 0
BytesIn: 0 BytesOut: 0
Forwarding: Enabled MTU: 1500
Broadcast Capability: Yes
Multicast Capability: Unknown
Ready; T=0.07/0.10 16:26:07

------------------------------------------------------------------------
netstat home
VM TCP/IP Netstat Level 510

IPv4 Home address entries:

Address Link
------- ------
192.168.0.51 ETH1

IPv6 Home address entries: None

Ready; T=0.07/0.10 16:26:13

----------------------------------------------------------------------------
netstat gate
VM TCP/IP Netstat Level 510

Known IPv4 gateways:

NetAddress FirstHop Flgs PktSz Subnet Mask Subnet Value Link
---------- -------- ---- ----- ----------- ------------ ------
Default 192.168.0.1 GS 1500 <none> ETH1
192.168.0.0 <direct> S 1500 <none> ETH1

Known IPv6 gateways: None

Ready; T=0.07/0.10 16:26:22

The corresponding device definition in tserver.cfg is

channel(0) local # channel 0 a local channel
cu devad(0xE20,2) path(0) resource(cu3172b) # 3172 For TCP/IP

cu3172b: cu 3172 # zVM Virtual CTC to local 3172 on Ethernet
interface local(1)
device(00) 3172 /dev/net2 # Ethernet Adapter
device(01) 3172 OFFLINE # Reserved
end cu3172b

and the ifconfig -a shows

lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask ff000000
inet/perf: recv size: 4096; send size: 8192; full-size frames: 1
inet/options: rfc1323
net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.50 netmask ffffff00 broadcast 192.168.0.255
inet/perf: recv size: 24576; send size: 24576; full-size frames: 1
inet/options: rfc1323
ether 00:09:6b:b0:5f:ca
net1: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
inet/perf: recv size: 24576; send size: 24576; full-size frames: 1
inet/options: rfc1323
ether 00:02:b3:62:9b:75
net2: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 0.0.0.0 netmask ff000000 broadcast 0.255.255.255
inet/perf: recv size: 24576; send size: 24576; full-size frames: 1
inet/options: rfc1323
ether 00:02:b3:62:9b:76

This is the network configuration as it appears in scoadmin. I have also tried to configure it as eeE devices instead of eeE8, but the result is the same.

********************************************************************************
** Configuration Manager *************************
********************************************************************************
** Hardware Protocol View Help **
********************************************************************************
*Current networking configuration: **
********************************************************************************
***HW Intel(R) PRO/100+(eeE8)-PCI Slot 0 Bus 1 Device 7 Function 0 **
** - TCP/IP **
** HW Intel(R) PRO/100+(eeE8)-PCI Slot 2 Bus 2 Device 4 Function 0 **
** - TCP/IP **
** HW Intel(R) PRO/100+(eeE8)-PCI Slot 2 Bus 2 Device 5 Function 0 **
** - TCP/IP **
** **
** **
** **
** **
** **
** **
** **
** **
** **
********************************************************************************
********************************************************************************
*Current configuration of the LAN software in this system **
********************************************************************************

----------------------

*********************** Internet Protocol Configuration *************************
** **
** **
** Host name |tserver01 | **
** DHCP client < > Yes <*> No **
** Domain name |tserver01 | **
** IP address |0 |.|0 |.|0 |.|0 | **
** Netmask |255|.|0 |.|0 |.|0 | **
** Broadcast address |0 |.|255|.|255|.|255| **
** Default router | |.| |.| |.| | **
** [ Advanced options ] **
** **
** **
** **
** **
** **
** **
** **
** **
**Enter host name of this machine **
*********************************************************************************
**[ OK ] [ Cancel ] [ Help ]**
*********************************************************************************

I have also checked, if the adapter is working. If I configure an ip address on the adapter it is reachable. So there cannot be an error with the cables.

Does anybody of you have an idea what might be wrong?

Mit freundlichen Grüßen / best regards

Franz Josef Pohlen

Pohlen (Mailinglist)

2006-02-15 16:41:43 UTC

Permalink

Hi Stephen,

just in the moment I have found the problem due to a hint of a friend. After
adding the adapters with scoadmin it is necessary to comment out the
adapters used by flex in the file /etc/confnet.d/inet/interface. Now my
network is running again. But thanks for your early reply.

Franz Josef

----- Original Message -----
From: "Stephen Frazier" <***@doc.state.ok.us>
To: <VMESA-***@LISTSERV.UARK.EDU>
Sent: Wednesday, February 15, 2006 5:36 PM
Subject: Re: [VMESA-L] I cannot get my VM TCPIP running on my t-server

The FSINA100 message when you start TCP/IP indicates that the

configuration does

not match the hardware. What level of FLEX-ES are you running? What kind

hardware? How many ethernet adapters are on your t-server? What kind of

adapters

are they? Which ones are attached to your network?

Post by Pohlen (Mailinglist)
cross posted to VM list and Flex-ES list
Hi all,
I have had big trouble with my ethernet adapters on my t-server. They
were all unusable, but now they are running again. I have started zVM
and can use the emulated non-SNA devices over my LAN. The only thing
which doesn't work up to now, is the tcpip network connection from the
zVM, which was surely ok before the error. FLEX-ES starts with no error
with all control units available but if I start the Ethernet interface
in zVM TCPIP (/dev/net2), flex-es produces an alert with the following
FSINA100 2006/02/15 09:03:04 ENETDEV: ALERT trace dump taken for device
0e20 (tserver01:/var/adm/flexes/tserver1/devtr.2036.0)

<snip>

Post by Pohlen (Mailinglist)
Does anybody of you have an idea what might be wrong?
Mit freundlichen Grüßen / best regards
Franz Josef Pohlen

--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%doc.state.ok.us

Stephen Frazier

2006-02-15 16:36:32 UTC

Permalink

The FSINA100 message when you start TCP/IP indicates that the configuration does
not match the hardware. What level of FLEX-ES are you running? What kind of
hardware? How many ethernet adapters are on your t-server? What kind of adapters
are they? Which ones are attached to your network?

<snip>

Post by Pohlen (Mailinglist)
Does anybody of you have an idea what might be wrong?
Mit freundlichen Grüßen / best regards
Franz Josef Pohlen

Gary Eheman

2006-02-15 17:10:38 UTC

Permalink

Unlike with Linux based FLEX-ES solutions, under UnixWare only one TCP/IP
stack at a time may exist on a NIC. That can be either UnixWare's (which is
happy to put one on any adapter it sees) or a mainframe o.s. like VM. When
you deleted and readded your adapters, you undid the customization that was
formerly done by the reseller who built the system to assure that UnixWare
would not attempt to put its stack on the adapter.

On Wed, 15 Feb 2006 17:41:43 +0100, Pohlen (Mailinglist)

Post by Pohlen (Mailinglist)
Hi Stephen,
just in the moment I have found the problem due to a hint of a friend. After
adding the adapters with scoadmin it is necessary to comment out the
adapters used by flex in the file /etc/confnet.d/inet/interface. Now my
network is running again. But thanks for your early reply.
Franz Josef
----- Original Message -----
Sent: Wednesday, February 15, 2006 5:36 PM
Subject: Re: [VMESA-L] I cannot get my VM TCPIP running on my t-server

The FSINA100 message when you start TCP/IP indicates that the

configuration does

not match the hardware. What level of FLEX-ES are you running? What kind

hardware? How many ethernet adapters are on your t-server? What kind of

adapters

are they? Which ones are attached to your network?

<snip>

Post by Pohlen (Mailinglist)
Does anybody of you have an idea what might be wrong?
Mit freundlichen Grüßen / best regards
Franz Josef Pohlen

=========================================================================

--
Gary Eheman
Fundamental Software, Inc