[ITM] Out of sync HUB TEMS?
"Battista, Joe" <[email protected]> Thu, 31 Oct 2013 14:09:19 +0000
| Newsgroups | gmane.comp.sysutils.tivoli.general |
|---|---|
| Message-ID | <CD2BE4CF4B56C0418FE90A2F0AA253F705A8E2FE__48801.3966278688$1383228651$gmane$org@SM-EXMAIL-P4.carefirst.com> |
--===============0592953172==
Content-Language: en-US
Content-Type: multipart/alternative;
boundary="_000_CD2BE4CF4B56C0418FE90A2F0AA253F705A8E2FESMEXMAILP4caref_"
--_000_CD2BE4CF4B56C0418FE90A2F0AA253F705A8E2FESMEXMAILP4caref_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
We recently upgraded to ITM 6.2.3 FP03. Our environment consists of a pair =
of HUB TEMS, (primary and hot-standby) and four Remote TEMS for our agents.=
We shut down our primary HUB which forced the failover to the hot-standby.=
Within a period of time we started receiving agent offline alerts which w=
e sort of expected since our Remote TEMS were failing over to the hot-stand=
by HUB. It's been a while since we left our hot-standby HUB run as the pri=
mary.
After closer review, we noticed some of the offline agent alerts were from =
servers that had been removed from our environment some time ago.
I see references to the servers that no longer exist in our environment in =
the QA1*.DB files on the hot-standby HUB but not on the primary HUB, specif=
ically tables QA1CSTSC.DB, QA1CSTSH.DB and QA1DNSAV.DB.
I assume this means in some way our HUB TEMS are out-of-sync? Is there an e=
asy way to get our hot-standby cleaned up and in-sync with the primary HUB?=
Thanks,
Joe
***************************************************************************=
****
Unauthorized interception of this communication could be a violation of Fed=
eral and State Law. This communication and any files transmitted with it ar=
e confidential and may contain protected health information. This communica=
tion is solely for the use of the person or entity to whom it was addressed=
. If you are not the intended recipient, any use, distribution, printing or=
acting in reliance on the contents of this message is strictly prohibited.=
If you have received this message in error, please notify the sender and d=
estroy any and all copies. =
Thank you..
***************************************************************************=
****
--_000_CD2BE4CF4B56C0418FE90A2F0AA253F705A8E2FESMEXMAILP4caref_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D">We recentl=
y upgraded to ITM 6.2.3 FP03. Our environment consists of a pair of HUB TEM=
S, (primary and hot-standby) and four Remote TEMS for our agents. We shut d=
own our primary HUB which forced the failover
to the hot-standby. Within a period of time we started receivin=
g agent offline alerts which we sort of expected since our Remote TEMS were=
failing over to the hot-standby HUB. It’s been a while since w=
e left our hot-standby HUB run as the primary.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D"><o:p> =
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D">After =
;closer review, we noticed some of the offline agent alerts were =
from servers that had been removed from our environment some time ago.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D">I see refe=
rences to the servers that no longer exist in our environment in the QA1*.D=
B files on the hot-standby HUB but not on the primary HUB, specifically tab=
les QA1CSTSC.DB, QA1CSTSH.DB and QA1DNSAV.DB.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D"><o:p> =
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D">I assume t=
his means in some way our HUB TEMS are out-of-sync? Is there an easy way to=
get our hot-standby cleaned up and in-sync with the primary HUB?<o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D"><o:p> =
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D"><o:p> =
;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D">Thanks, <o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN" style=3D"color:#1F497D">Joe =
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p> </o:p></spa=
n></p>
<p class=3D"MsoNormal"><o:p> </o:p></p>
</div>
<br clear=3Dall> **********************************************************=
********************* <br>=0D
=0D
Unauthorized interception of this communication could be a violation of Fed=
eral and State Law. This communication and any files transmitted with it ar=
e confidential and may contain protected health information. This communica=
tion is solely for the use of the person or entity to whom it was addressed=
. If you are not the intended recipient, any use, distribution, printing or=
acting in reliance on the contents of this message is strictly prohibited.=
If you have received this message in error, please notify the sender and d=
estroy any and all copies. Thank you.. <br>=0D
=0D
***************************************************************************=
**** <br>=0D
</body>
</html>
--_000_CD2BE4CF4B56C0418FE90A2F0AA253F705A8E2FESMEXMAILP4caref_--
--===============0592953172==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]
--===============0592953172==--