|
At
this point, our organization has a policy to not use load balancers for
"failover" purposes between two servers. If we need that, we are supposed
to look into full blown clustering. I know, it all depends on how you look
at things. :) So, I'm asking questions on both fronts to see if
we can't get something that makes a failure totally hands
off.
How about putting the TEC servers behind an SLB and have
one of the servers listed as the primary, when it goes down, the SLB will send
traffic to the other TEC Server...
I
suggested exactly that idea of specifying more than one server. Our TEC
folks rejected it, because they want to make sure that all systems sending
events to TEC are always sending to the same TEC. If we specified both,
there would be a chance that we would be sending to a different TEC than the
rest of the company.
I'll
follow up on the TEC side.
Thanks!
Actually, you are asking the wrong folks. The session is established
using the tec_create_handle call in the TEC EEIF library. So how that is
done is TEC issue, not a NetView one.
That said, I believe that once
the session is started, it is persistent, and would not be affected unless
it fails for some reason (network connection drops for example) or is
deliberately stopped, as you suggested.
But the TEC conf file is
supposed to permit you to define a backup server in the ServerLocation
field. As I understood it, this fancy footwork by your staff is unnecessary.
Is TEC no longer supporting that?
James Shanks
Level 3 Support for
Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software
Group
 "Treptow, Craig"
<Treptow.Craig@principal.com>
"Treptow, Craig"
<Treptow.Craig@principal.com>
Sent by:
owner-nv-l@lists.us.ibm.com
01/25/2005 03:34 PM
|
|
Hi.
We're running NV 7.1.4 on AIX 5.1. We forward events to TEC and
specify a DNS name for the TEC server. Our TEC folks are working on a
solution whereby they can use DDNS to update the TEC server entry and point
it from the broken server to the backup server.
Does anybody know if
we'll have to touch Netview in some way when they do that? I suspect
that NV only looks up the name when nvserverd starts and will use that until
a "nvtecia -reload" is performed, or the daemon is bounced.
I'm not
in a good position to test this today, so if somebody knows off-hand, that
would be really
helpful.
Thanks!
Craig
-----Message
Disclaimer-----
This e-mail message is intended only for the use of
the individual or
entity to which it is addressed, and may contain
information that is
privileged, confidential and exempt from disclosure
under applicable law.
If you are not the intended recipient, any
dissemination, distribution or
copying of this communication is strictly
prohibited. If you have
received this communication in error, please
notify us immediately by
reply email to Connect@principal.com and delete
or destroy all copies of
the original message and attachments thereto.
Email sent to or from the
Principal Financial Group or any of its member
companies may be retained
as required by law or
regulation.
Nothing in this message is intended to constitute an
Electronic signature
for purposes of the Uniform Electronic Transactions
Act (UETA) or the
Electronic Signatures in Global and National Commerce
Act ("E-Sign")
unless a specific statement to the contrary is included in
this message.
-----Message Disclaimer-----
This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect@principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.
Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.
-----Message Disclaimer-----
This e-mail message is intended only for the use of the individual or
entity to which it is addressed, and may contain information that is
privileged, confidential and exempt from disclosure under applicable law.
If you are not the intended recipient, any dissemination, distribution or
copying of this communication is strictly prohibited. If you have
received this communication in error, please notify us immediately by
reply email to Connect@principal.com and delete or destroy all copies of
the original message and attachments thereto. Email sent to or from the
Principal Financial Group or any of its member companies may be retained
as required by law or regulation.
Nothing in this message is intended to constitute an Electronic signature
for purposes of the Uniform Electronic Transactions Act (UETA) or the
Electronic Signatures in Global and National Commerce Act ("E-Sign")
unless a specific statement to the contrary is included in this message.
|
