Hi,
what about routing? Is it possible that the default route does point to an
inactive interface?
Kind regards,
Tobias.
--
For LINUX-390 subscribe / signoff / archive access
Hi,
what about routing? Is it possible that the default route does point to an
inactive interface?
Kind regards,
Tobias.
PS: Sorry i forgot the subject.
--
For LINUX-390 subscribe /
Ron,
the MAC-address for a VSWITCH interface is defined by z/VM. Can you
check somehow if this MAC-address changes during upgrade - for instance
in z/VM CP with command CP Q VSWITCH DETAILS? If yes, the problem seems
to be related to Novell bugzilla 617373.
Kind regards, Ursula Braun, IBM
I have been trying to REHL6 on a z114 to authenticate to an
Active Directory Domain Controller with LDAP.
What I was hoping was to be directed to a document or
procedure to help me along.
The manuals are very terse. I was also emailed the
certificate and the books are all about download it.
I
Re worded so it makes sense{8^)
I have been trying to configure REHL6 on a z114 to
authenticate to an Active Directory Domain Controller
with LDAP.
What I was hoping was to be directed to a document or
procedure to help me along.
I think I have it all working but the TLS.
The manuals are
Greek to me but hopefully somebody who is LDAP/AD knowledgeable will respond.
Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
301-594-7474
-Original Message-
From: Dickinson, Eric (CIT)
Sent: Friday, February 03, 2012 9:18 AM
To:
I reworded and resent it so it makes more sense.
On 02/03/2012 09:23 AM, Bauer, Bobby (NIH/CIT) [E] wrote:
Greek to me but hopefully somebody who is LDAP/AD knowledgeable will respond.
Bobby Bauer
Center for Information Technology
National Institutes of Health
Bethesda, MD 20892-5628
Tobias,
I will have to further testing, but I think you have come up with the cause of
our problem. I am just going to have to figure out the best way to fix it.
Here is the problem:
1. Almost all of our systems have more than one network interface.
2. So in order to avoid an error message,
So you can modify /etc/udev/rules.d/30-net_persistent_names.rules
For the servers we have with more than 1 interface, it contains this:
SUBSYSTEM==net, ACTION==add, ENV{PHYSDEVPATH}==*0.0.3000,
IMPORT=/lib/udev/rename_netiface %k eth0
SUBSYSTEM==net, ACTION==add, ENV{PHYSDEVPATH}==*0.0.4000,
On 2/3/2012 at 10:13 AM, Ron Foster at Baldor-IS rfos...@baldor.com
wrote:
3. You may ask why we used qeth-bus-ccw-0.0.0700 instead of the short
interface name eth0. The reason why is that in our experience, the short
interface names
have this habit of changing. We would come in some
10 matches
Mail list logo