Interesting it works for you, our setup is:
NICDEF 0700 TYPE QDIO DEV 3 LAN SYSTEM VSW1
NICDEF 0710 TYPE QDIO DEV 3 LAN SYSTEM VSW1
zlin0068:~ # ifconfig -a
eth0 Link encap:Ethernet HWaddr 02:03:00:00:00:22
inet addr:131.97.122.248 Bcast:131.97.122.255 Mask:255.255.255.128
inet6 addr: fe80::203:0:100:22/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:473 errors:0 dropped:0 overruns:0 frame:0
TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:39296 (38.3 Kb) TX bytes:578 (578.0 b)
eth1 Link encap:Ethernet HWaddr 02:03:00:00:00:2E
inet addr:131.97.122.245 Bcast:131.97.122.255 Mask:255.255.255.128
inet6 addr: fe80::203:0:100:2e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:2189 errors:0 dropped:0 overruns:0 frame:0
TX packets:2492 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:490570 (479.0 Kb) TX bytes:1193213 (1.1 Mb)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:1230 errors:0 dropped:0 overruns:0 frame:0
TX packets:1230 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68126 (66.5 Kb) TX bytes:68126 (66.5 Kb)
/etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='static'
IPADDR='131.97.122.248/25'
BROADCAST=''
STARTMODE='auto'
NAME='OSA Express Network card (0.0.0700)'
ETHTOOL_OPTIONS=''
INTERFACETYPE='qeth'
MTU=''
NETWORK=''
REMOTE_IPADDR=''
USERCONTROL='no'
/etc/sysconfig/network/ifcfg-eth1
BOOTPROTO='static'
BROADCAST=''
ETHTOOL_OPTIONS=''
INTERFACETYPE='qeth'
IPADDR='131.97.122.245/25'
MTU=''
NAME='OSA Express Network card (0.0.0710)'
NETWORK=''
REMOTE_IPADDR=''
STARTMODE='auto'
USERCONTROL='no'
/etc/udev/rules.d/51-qeth-0.0.0700.rules
# Configure qeth device at 0.0.0700/0.0.0701/0.0.0702
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="qeth", IMPORT{program}="collect
0.0.0700 %k 0.0.0700 0.0.0701 0.0.0702 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0700", IMPORT{program}="collect
0.0.0700 %k 0.0.0700 0.0.0701 0.0.0702 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0701", IMPORT{program}="collect
0.0.0700 %k 0.0.0700 0.0.0701 0.0.0702 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0702", IMPORT{program}="collect
0.0.0700 %k 0.0.0700 0.0.0701 0.0.0702 qeth"
TEST=="[ccwgroup/0.0.0700]", GOTO="qeth-0.0.0700-end"
ACTION=="add", SUBSYSTEM=="ccw", ENV{COLLECT_0.0.0700}=="0",
ATTR{[drivers/ccwgroup:qeth]group}="0.0.0700,0.0.0701,0.0.0702"
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="qeth",
ENV{COLLECT_0.0.0700}=="0",
ATTR{[drivers/ccwgroup:qeth]group}="0.0.0700,0.0.0701,0.0.0702"
LABEL="qeth-0.0.0700-end"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.0700",
ATTR{portname}="ZLINUX"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.0700", ATTR{portno}="0"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.0700", ATTR{layer2}="0"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.0700", ATTR{online}="1"
/etc/udev/rules.d/51-qeth-0.0.0710.rules
# Configure qeth device at 0.0.0710/0.0.0711/0.0.0712
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="qeth", IMPORT{program}="collect
0.0.0710 %k 0.0.0710 0.0.0711 0.0.0712 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0710", IMPORT{program}="collect
0.0.0710 %k 0.0.0710 0.0.0711 0.0.0712 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0711", IMPORT{program}="collect
0.0.0710 %k 0.0.0710 0.0.0711 0.0.0712 qeth"
ACTION=="add", SUBSYSTEM=="ccw", KERNEL=="0.0.0712", IMPORT{program}="collect
0.0.0710 %k 0.0.0710 0.0.0711 0.0.0712 qeth"
TEST=="[ccwgroup/0.0.0710]", GOTO="qeth-0.0.0710-end"
ACTION=="add", SUBSYSTEM=="ccw", ENV{COLLECT_0.0.0710}=="0",
ATTR{[drivers/ccwgroup:qeth]group}="0.0.0710,0.0.0711,0.0.0712"
ACTION=="add", SUBSYSTEM=="drivers", KERNEL=="qeth",
ENV{COLLECT_0.0.0710}=="0",
ATTR{[drivers/ccwgroup:qeth]group}="0.0.0710,0.0.0711,0.0.0712"
LABEL="qeth-0.0.0710-end"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.0710",
ATTR{portname}="ZLINUX1"
# have tested 0 and 1 in PORTNO below, same result
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.0710", ATTR{portno}="0"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.0710", ATTR{layer2}="0"
ACTION=="add", SUBSYSTEM=="ccwgroup", KERNEL=="0.0.0710", ATTR{online}="1"
___________________________________________
Tore Agblad
Volvo Information Technology
Infrastructure Mainframe Design & Development, Linux servers
Dept 4352 DA1S
SE-405 08, Gothenburg Sweden
Telephone: +46-31-3233569
E-mail: [email protected]
http://www.volvo.com/volvoit/global/en-gb/
-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Edmund R.
MacKenty
Sent: den 25 augusti 2010 15:47
To: [email protected]
Subject: Re: Anyone have 2 NICs on SLES11 SP1 working ?
On Tuesday, August 24, 2010 02:54:31 am you wrote:
> Hi there.
> I have put this question here earlier this summer and I used the
> proposed solution to add one more IPaddress to the same NIC.
> That works fine IPwise, but we need two IPaddresses for setting up two WAS
> Deploymnet Mgrs in same server, and it does not work on same NIC for this
> type of usage. We got port conflicts.
> In the old SLES10 it works perfect with 3 NICs used by three different
> WAS Deploy Mgrs.
> So there is a difference here, I can not find the reason.
>
> I can config two NICs, and it 'works' the way only one usable at any time
> from outside. ssh two any of them locally from inside works however (if I
> remember my tests this summer correctly)
> Also it is possible to take the other interface up
> ifconfig eth1 up
> and eth0 becomes unavailable.
We've set up multiple NICs on SLES 11.0 with no problems. Not sure if we've
done that on SP1, though. Havn't ever seen them interferring with each other.
What sort of NIC is this? Hipersocket? VSWITCH? Do you perhaps have them
using the same virtual device numbers? I would imagine that would break
things pretty badly.
- MacK.
-----
Edmund R. MacKenty
Software Architect
Rocket Software
275 Grove Street - Newton, MA 02466-2272 - USA
Tel: +1.617.614.4321
Email: [email protected]
Web: www.rocketsoftware.com
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
----------------------------------------------------------------------
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
----------------------------------------------------------------------
For more information on Linux on System z, visit
http://wiki.linuxvm.org/
