Yes:

q vswitch name tsm1 acc
VSWITCH SYSTEM TSM1     Type: VSWITCH Connected: 11   Maxconn: INFINITE    
  PERSISTENT  RESTRICTED    NONROUTER                 Accounting: OFF      
  VLAN Aware  Default VLAN: 0001    Default Porttype: Access  GVRP: Enabled
              Native  VLAN: 0001    VLAN Counters: OFF                     
<snip>
      NLZLX213 Porttype: Access VLAN: 0760                                    
      NLZLX214 Porttype: Access VLAN: 0760                                    
      NLZLX215 Porttype: Access VLAN: 0760                                    
      SYSTEM   Porttype: Access VLAN: 0001                                    
  Portname: DEVHW1A    RDEV: EC80.P00 Controller: BIVSWOS1 VDEV:  EC80        
  Portname: DEVHW2A    RDEV: EC90.P00 Controller: BIVSWOS1 VDEV:  EC90 BACKUP 
Ready; T=0.01/0.01 13:41:52                                                   

Regards, Berry. 

-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Agblad 
Tore
Sent: woensdag 17 juni 2009 13:39
To: [email protected]
Subject: Re: How to activate 2nd nic

Did you GRANT the Linux to the vswitch ?

Cordialement / Vriendelijke Groeten / Best Regards / Med Vänliga Hälsningar
  Tore Agblad

   Volvo Information Technology
   Infrastructure Mainframe Design & Development
   SE-405 08, Gothenburg  Sweden
   E-mail: [email protected]

   http://www.volvo.com/volvoit/global/en-gb/
________________________________________
From: Linux on 390 Port [[email protected]] On Behalf Of van Sleeuwen, 
Berry [[email protected]]
Sent: Wednesday, June 17, 2009 13:24
To: [email protected]
Subject: How to activate 2nd nic

Hello listers,

I'm trying to get the second nic working in an SLES10 guest. In one guest I 
succeeded but I don't know why. I had been tinkering in several places 
including with yast. But once it worked I still didn't figure out what the 
trick was.

The guest has two nic's defined in VM, both qdio, connected to a vswitch.

nlzlx213:/ # vmcp q v nic
Adapter 0F00.P00 Type: QDIO      Name: devclaw     Devices: 3
  MAC: 02-00-00-00-00-11         VSWITCH: SYSTEM OSNLINUX
Adapter 0F10.P00 Type: QDIO      Name: devclaw     Devices: 3
  MAC: 02-00-00-00-00-12         VSWITCH: SYSTEM TSM1

The ifconfig shows eth0, eth1 and lo. But the nlzlx214, the second machine, 
(almost) identical to the nlzlx213 only shows eth0 and lo.
Activating eth1 shows:

nlzlx214:~ # ifup eth1
Interface eth1 is not available

rcnetwork restart only restarts eth0.

I also tried to activate with yast, the eth0 (device f00) show as just f00. The 
devices that should be used for eth1, f10-f12, are listed seperatly. After 
creating the configuration files in /etc/sysconfig/network, just like in the 
nlzlx213 machine, I do see the config on device f10, but f11 and f12 show not 
configured.

Somewhere along the route I have missed a step. I expected to create the 
configuration in /etc/sysconfig/network would be enough but apparently I need 
to do something more. So the question, how to activate and configure the second 
nic? I do prefer to do this without yast, not only because I don't succeed with 
yast as well, but also to see what has to be done here.


Met vriendelijke groet/With kind regards, Berry van Sleeuwen Flight Forum 3000 
5657 EW Eindhoven

( +31 (0)6 22564276





Atos Origin <http://www.atosorigin.com/>

MO OC Mainframe Services









----------------------------------------------------------------------
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 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 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
ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to