On Tuesday, 08/25/2009 at 09:59 EDT, Rich Smrcina
wrote:
> The clouds parted, beams of sun streak through, it is a good day to be a
> sysprog.
And a heavenly chorus was heard. You make it sound like I'm an
opinionated old goat who never changes his mind on anything. Oh. I see
your point.
David Boyes wrote:
On 8/24/09 7:12 PM, "Alan Altmark" wrote:
I am rapidly moving to the opinion that VM TCP/IP should use a VSWITCH and
let the VSWITCH handle failover at the hardware level rather than needing
multiple IP addresses, VIPAs, and dynamic routing.
When VSWITCHes first became
On 8/24/09 7:12 PM, "Alan Altmark" wrote:
> I am rapidly moving to the opinion that VM TCP/IP should use a VSWITCH and
> let the VSWITCH handle failover at the hardware level rather than needing
> multiple IP addresses, VIPAs, and dynamic routing.
> When VSWITCHes first became available, I was
Thank you Miguel,
That did it.
> Shimon,
>
> Stop the interface with IFCONFIG VSECM DOWN first. It turns out that
> IFCONFIG doesn't use the actual device status to decide whether an
> interface is UP or DOWN...it considers a device UP if it has usable routes
> (i.e. it can actually send traffic
TCPIP works really nicely using a VSWITCH... at my current location, we've
reduced TCPIP's role to the VM stack only -- and share the VSWITCH with
Linux guests. We can bounce TCPIP without affecting anyone but the VM
sysprogs telnetting in..
I'm a fan of letting the vswitch controllers manage t
On Monday, 08/24/2009 at 02:19 EDT, "Dean, David (I/S)"
wrote:
> We had a situation where one of our OSA links died, but failover did not
> occur. It appeared to us that the zVM was not aware that the card was
actually
> ?down?. This seemed similar to what you were referencing. I could be
e IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf
Of Miguel Delapaz
Sent: Monday, August 24, 2009 2:01 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: IFCONFIG to -REMOVE a link
IFCONFIG doesn't display information about VSWITCHes or their controllers...so
I'm not sure what
IFCONFIG doesn't display information about VSWITCHes or their
controllers...so I'm not sure what you're referring to. Could you clarify?
Regards,
Miguel Delapaz
z/VM Development
> "Dean, David (I/S)"
>
> Yep, and if you have two controllers for failover to two OSA’s this
> is a problem … am I u
IBMVM@LISTSERV.UARK.EDU
Subject: Re: IFCONFIG to -REMOVE a link
Shimon,
Stop the interface with IFCONFIG VSECM DOWN first. It turns out that IFCONFIG
doesn't use the actual device status to decide whether an interface is UP or
DOWN...it considers a device UP if it has usable routes (i.e. it can actu
that :-)
Regards,
Miguel Delapaz
z/VM Development
The IBM z/VM Operating System wrote on 08/23/2009
05:01:55 AM:
> Hi,
> I tried to use IFCONFIG to remove a link. According to the help file
> the interface must be inactive first. I assumed that an interface which
is
> "DOWN"
Hi,
I tried to use IFCONFIG to remove a link. According to the help file
the interface must be inactive first. I assumed that an interface which is
"DOWN" can be considered "inactive", but apparently I was wrong:
IFCONFIG VSECM
VSECMINET ADDR: 10.1.5.2 P-T-P: 10.1
11 matches
Mail list logo
