Default route in /etc/sysconfig/network.

On Thu, Oct 30, 2014 at 10:26 AM, Chase, John <[email protected]> wrote:

> No.
>
>   -jc-
>
> > -----Original Message-----
> > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
> Ambros, Thomas
> > Sent: Thursday, October 30, 2014 9:11 AM
> > To: [email protected]
> > Subject: Re: Linux guests on DR machine not reachable
> >
> > Are you running mproute?
> >
> > Thomas Ambros
> > zEnterprise Operating Systems
> > zEnterprise Systems Management
> > 518-436-6433
> >
> > -----Original Message-----
> > From: Linux on 390 Port [mailto:[email protected]] On Behalf Of
> Chase, John
> > Sent: Thursday, October 30, 2014 10:01
> > To: [email protected]
> > Subject: Linux guests on DR machine not reachable
> >
> > Cross-posted to IBMVM and LINUX390 lists
> >
> > Greetings.
> >
> > We're bringing up z/VM and Linux guests for the first time at a D/R
> exercise.  Since we have our own
> > CBU "warm site", we create an isolated network to be used for the D/R
> exercise.  The primary internal
> > network is prefixed 10.1 and the isolated D/R network is prefixed 10.2.
> >
> > After z/VM (6.2, non-SSI) IPLs, we logon TCPMAINT and edit PROFILE TCPIP
> to change the HOME and
> > DEFAULTNET IP addresses from 10.1.xxx.yyy to 10.2.xxx.yyy, then shut
> down and restart TCPIP.  z/VM is
> > now reachable from non-mainframe devices plugged into the isolated
> network (e.g., Ping from a laptop
> > works fine; 3270 emulator sessions establish via non-ICC ports).
> >
> > Next we login to a Linux (RHEL 6.3 and 6.5) guest (3270 console), where
> we had pre-configured a
> > "clone" of the ifcfg-eth0 file to specify 10.2 (instead of 10.1) in all
> the appropriate places.  We
> > rename ("mv") the "prod" and "D/R" copies so that ifcfg-eth0 now
> specifies 10.2 instead of 10.1 in all
> > the right places.  We stop and restart network services, but Linux is
> not ping-able from outside.  OK
> > let's reboot Linux.  No change; still can't ping Linux from outside the
> mainframe but within the
> > isolated network.  OK, we'll just bounce the whole virtual machine
> (SIGNAL SHUTDOWN followed by
> > XAUTOLOG from OPERATOR).  That didn't work, either.  We didn't notice
> any network-related error
> > message as Linux came up again.
> >
> > Not much to go on, but can anybody think of what we might have missed in
> reconfiguring Linux to "play"
> > in the isolated (10.2) network?
> >
> > TIA,
> >
> >     -jc-
> >
> > **********************************************************************
> > Information contained in this e-mail message and in any attachments
> thereto is confidential. If you
> > are not the intended recipient, please destroy this message, delete any
> copies held on your systems,
> > notify the sender immediately, and refrain from using or disclosing all
> or any part of its content to
> > any other person.
> >
> > ----------------------------------------------------------------------
> > 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/
> >
> >
> > This communication may contain privileged and/or confidential
> information. It is intended solely for
> > the use of the addressee. If you are not the intended recipient, you are
> strictly prohibited from
> > disclosing, copying, distributing or using any of this information. If
> you received this communication
> > in error, please contact the sender immediately and destroy the material
> in its entirety, whether
> > electronic or hard copy. This communication may contain nonpublic
> personal information about consumers
> > subject to the restrictions of the Gramm-Leach-Bliley Act. You may not
> directly or indirectly reuse or
> > redisclose such information for any purpose other than to provide the
> services for which you are
> > receiving the information.
> >
> > 127 Public Square, Cleveland, OH 44114
> > If you prefer not to receive future e-mail offers for products or
> services from Key send an e-mail to
> > mailto:[email protected] with 'No Promotional E-mails' in the SUBJECT
> line.
> >
> > ----------------------------------------------------------------------
> > 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/
>

----------------------------------------------------------------------
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/

Reply via email to