Re-defining osa addresses on zVM for a SuSE 9x server
to another OSA card (OSA Express Gb LX). This is the
first time this card is being used and the link does not come up.
(example
DEDICATE 1D00 1F20
DEDICATE 1D01 1F21
DEDICATE 1D02 1F22 )
Before starting round two with our network guy, I was wondering
if the portname shown below could hurt? This is the name of
the old osa card still being used elsewhere.
I followed a Mark Post post to see/set portname using Yast. It was
already blank but I saved it anyway. So where is the below portname
coming from? Does it matter?
Thanks.
Setting up network interfaces:
qeth: Device 0.0.1d00/0.0.1d01/0.0.1d02 is a OSD Express card (level: 0635)
with link type OSD_1000 (portname: osacssd)
qeth: LAN on card 0.0.1d00 if offline! Continuing softsetup.
qeth: Hardware IP fragmentation not supported on eth0
qeth: VLAN enabled
qeth: Multicast enabled
qeth: IPv6 startlan failed on eth0
qeth: Broadcast enabled
qeth: Using SW checksumming on eth0.
qeth: Outbound TSO not supported on eth0
lo
lo IP address: 127.0.0.1/8
ADDRCONF(NETDEV_UP): eth0: link is not ready
qeth: Could not register IP address 172.26.49.90 (rc=0xe080/57472)
qeth: Could not register IP address 172.26.49.91 (rc=0xe080/57472)
qeth: Could not register IP address 172.26.49.92 (rc=0xe080/57472)
[1A..done eth0
eth0 configuration: qeth-bus-ccw-0.0.1d00
eth0 IP address: 172.26.49.90/24
secondary eth0:0 IP address: 172.26.49.91/24
secondary eth0:1 IP address: 172.26.49.92/24
[1A..doneSetting up service network . . . . . . . . . . . . .
.
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
