Hello Marcy, Indeed we have two VM systems and we once had a MAC prefix. But the prefix had been removed some time ago (actually by accident but it had not been setup again since then).
I was told that duplicate MAC addresses would not be a problem in a TCPIP connection. Only when for instance a CCL is running there could be a problem with duplicate MAC's on SNA connections as we had discovered a few years ago. Since we have been running with duplicate MAC addresses for quite some time I would expect this not to be a problem that hits us only last Friday. I would expect that we either would have had problems with this for the last 3 years or not at all. Up untill now I would say the latter is the case. So the question would be if in IP connections, is it realy a problem to have duplicate MAC addresses? Regards, Berry. -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of Marcy Cortes Sent: vrijdag 30 oktober 2009 14:59 To: [email protected] Subject: Re: Guest network connection error Berry, it looks like you are using Layer 2 (type ethernet) with no MAC prefix assigned perhaps? Could you have more than one VM system there? You might have duplicate MAC addresses. Marcy "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -----Original Message----- From: Linux on 390 Port [mailto:[email protected]] On Behalf Of van Sleeuwen, Berry Sent: Friday, October 30, 2009 5:04 AM To: [email protected] Subject: Re: [LINUX-390] Guest network connection error 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 ---------------------------------------------------------------------- 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
ÿþD i t b e r i c h t i s v e r t r o u w e l i j k e n k a n g e h e i m e i n f o r m a t i e b e v a t t e n e n k e l b e s t e m d v o o r d e g e a d r e s s e e r d e . I n d i e n d i t b e r i c h t n i e t v o o r u i s b e s t e m d , v e r z o e k e n w i j u d i t o n m i d d e l l i j k a a n o n s t e m e l d e n e n h e t b e r i c h t t e v e r n i e t i g e n . A a n g e z i e n d e i n t e g r i t e i t v a n h e t b e r i c h t n i e t v e i l i g g e s t e l d i s m i d d e l s v e r z e n d i n g v i a i n t e r n e t , k a n A t o s O r i g i n n i e t a a n s p r a k e l i j k w o r d e n g e h o u d e n v o o r d e i n h o u d d a a r v a n . H o e w e l w i j o n s i n s p a n n e n e e n v i r u s v r i j n e t w e r k t e h a n t e r e n , g e v e n w i j g e e n e n k e l e g a r a n t i e d a t d i t b e r i c h t v i r u s v r i j i s , n o c h a a n v a a r d e n w i j e n i g e a a n s p r a k e l i j k h e i d v o o r d e m o g e l i j k e a a n w e z i g h e i d v a n e e n v i r u s i n d i t b e r i c h t . O p a l o n z e r e c h t s v e r h o u d i n g e n , a a n b i e d i n g e n e n o v e r e e n k o m s t e n w a a r o n d e r A t o s O r i g i n g o e d e r e n e n / o f d i e n s t e n l e v e r t z i j n m e t u i t s l u i t i n g v a n a l l e a n d e r e v o o r w a a r d e n d e L e v e r i n g s v o o r w a a r d e n v a n A t o s O r i g i n v a n t o e p a s s i n g . D e z e w o r d e n u o p a a n v r a a g d i r e c t k o s t e l o o s t o e g e z o n d e n . T h i s e - m a i l a n d t h e d o c u m e n t s a t t a c h e d a r e c o n f i d e n t i a l a n d i n t e n d e d s o l e l y f o r t h e a d d r e s s e e ; i t m a y a l s o b e p r i v i l e g e d . I f y o u r e c e i v e t h i s e - m a i l i n e r r o r , p l e a s e n o t i f y t h e s e n d e r i m m e d i a t e l y a n d d e s t r o y i t . A s i t s i n t e g r i t y c a n n o t b e s e c u r e d o n t h e I n t e r n e t , t h e A t o s O r i g i n g r o u p l i a b i l i t y c a n n o t b e t r i g g e r e d f o r t h e m e s s a g e c o n t e n t . A l t h o u g h t h e s e n d e r e n d e a v o u r s t o m a i n t a i n a c o m p u t e r v i r u s - f r e e n e t w o r k , t h e s e n d e r d o e s n o t w a r r a n t t h a t t h i s t r a n s m i s s i o n i s v i r u s - f r e e a n d w i l l n o t b e l i a b l e f o r a n y d a m a g e s r e s u l t i n g f r o m a n y v i r u s t r a n s m i t t e d . O n a l l o f f e r s a n d a g r e e m e n t s u n d e r w h i c h A t o s O r i g i n s u p p l i e s g o o d s a n d / o r s e r v i c e s o f w h a t e v e r n a t u r e , t h e T e r m s o f D e l i v e r y f r o m A t o s O r i g i n e x c l u s i v e l y a p p l y . T h e T e r m s o f D e l i v e r y s h a l l b e p r o m p t l y s u b m i t t e d t o y o u o n y o u r r e q u e s t . A t o s O r i g i n N e d e r l a n d B . V . / U t r e c h t K v K U t r e c h t 3 0 1 3 2 7 6 2
