Hi Jonathan,

Yes they are. All guests are allowed on the vswitch with vlan 105. And
they all register on the vswitch with the correct vlan and IP address.

The TMR registers as:
Adapter Owner: NLPTMR01 NIC: 0F00.P00 Name: DEVCLAW                 
  Porttype: Access                                                  
  RX Packets: 5907581    Discarded: 0          Errors: 0            
  TX Packets: 10793515   Discarded: 0          Errors: 0            
  RX Bytes: 6753504379           TX Bytes: 14545624744              
  Device: 0F02  Unit: 002   Role: DATA       vPort: 0105  Index: 0105
  VLAN: IPv4 0105 Assigned by system                                
  VLAN: IPv6 0105 Assigned by system                                
  Options: Broadcast Multicast IPv6 IPv4 VLAN                       
    Unicast IP Addresses:                                           
      161.89.54.127        MAC: 02-00-00-00-00-26                   
      FE80::200:0:100:26   MAC: 02-00-00-00-00-26 Local             
    Multicast IP Addresses:                                         
      224.0.0.1            MAC: 01-00-5E-00-00-01                   
      FF02::1              MAC: 33-33-00-00-00-01                   
      FF02::1:FF00:26      MAC: 33-33-FF-00-00-26 Local             

It's similar for all other guests.

Berry.
 

-----Original Message-----
From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
Quay, Jonathan (IHG)
Sent: vrijdag 30 oktober 2009 12:50
To: [email protected]
Subject: Re: Guest network connection error

Berry,
 
Do the routing tables on the 3 linux instances look identical?  Can you
see all the vswitches register all the IPs?  Usually when we have a
problem like this its ACL's.

________________________________

From: Linux on 390 Port on behalf of van Sleeuwen, Berry
Sent: Fri 10/30/2009 5:41 AM
To: [email protected]
Subject: Guest network connection error



Hello listers,

We have a group of 3 SLES8 guests running Tivoli. Two of them, TEC and
TGW, have a fully functional network connection. But the third, the TMR,
can't connect to the outside world. This is the case since last Friday,
after a reboot of the guest.

The guests run on zVM 5.4 RSU 802. The guests are connected to two
VSWITCHes. One is the production network and the second is a dedicated
network for TSM backup purposes. Accessing the TMR can not be done from
outside the network. But we can logon to the TEC and then connect to the
TMR from there. So I'd expect the connection within VM (vswitch and
such) is correct.

Now we are puzzeled as to how to proceed. We have been working with
several groups (network, linux, VM etc) to get to the root of this
problem but with no success so far. The network configs in all 3 guests
are the same, other than the obvious IP addresses. We did see that a
ping had been travelling through the backup network but disabling this
network didn't make the production network available. Restarting the
network, detach/define of the NIC etc didn't help either.

Do you have any suggestions what we can do next?

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 CF SC 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