RE: ITM 6.2.3 FP2 is FTO totally broken?

Hi Yes
Which is precisely why I configured both WPA's to connect to the Primary hub and secondary to the secondary. The "TEMS list" configuration item  on the other hand points to the TEMS where the WPA is running.

When the primary is gone and the secondary becomes acting. It's WPA would service the other agents that need HTEMS connection, since these will have switched TEMS to the secondary now acting. Hence the TEMS list for the secondary must point to the secondary TEMS.

/Gus





________________________________
From: [email protected] [mailto:[email protected]] On Behalf Of John Alvord
Sent: den 14 november 2012 00:16
To: Discussion list for Tivoli product and Tivoli Ready products.
Subject: Re: [TME10] ITM 6.2.3 FP2 is FTO totally broken?

Much of the redundancy scenarios would be cases where server running the hub TEMS/primary role is either not functional [Building collapse perchance] or where there is a network outage that isolates the system running TEMS/primary role.  In that case, having a WPA on that system which might connect to another hub TEMS isn't much value. It would be far more redundant to have a WPA that is on each TEMS hub and remote and configured to take the workload that the TEMS would normally handle.

Lots of people only test the things that area easy to test... like stopping the hub TEMS/primary. But in real life, things are usually more pervasive.

Regards,



John Alvord - Ph: 1-720-396-2788    Cell: none
Customer Support - Tivoli Software - jalvord-r/[email protected]<mailto:[email protected]>
Advisory Engineer - Tivoli Monitoring - ITM infrastructure
Follow us on Twitter! @Tivolisupport<http://twitter.com/TivoliSupport> and Facebook<https://www.facebook.com/IBMTivoliSupport>
Personalize your support needs with the IBM Support Portal<http://www.ibm.com/support/electronicsupport/>
Use Service Request<http://www.ibm.com/software/support/servicerequest/quick_start.html> to get assistance!
For emails regarding a PMR, copy [email protected]<mailto:[email protected]>
For secure browser uploads: https://www.ecurep.ibm.com/app/upload
For Customer Support guidance: IBM Software Support Handbook<http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html>

<http://twitter.com/TivoliSupport>





From:        Jay Slay <[email protected]>
To:        "Discussion list for Tivoli product and Tivoli Ready products." <[email protected]>,
Date:        11/13/2012 07:55 AM
Subject:        Re: [TME10] ITM 6.2.3 FP2 is FTO totally broken?
Sent by:        [email protected]
________________________________



John,

Most folks (at least the ones I have talked to) configure their WPA's for failover using both the primary and standby TEMS.  While you are correct, the WPA can't log into the backup when its the backup, it can when the primary fails and the backup becomes the acting HUB.  That is (hopefully) the only case in which your WPA's couldn't contact the primary...during a failover.

Regards,


On Nov 13, 2012, at 10:33 AM, John Alvord <jalvord-r/[email protected]<mailto:[email protected]>> wrote:

I am really confused.

Warehouse Proxy Agents are agents like any other. They are made part of a system generated MSL that represents all WPAs. There are a few situations which run at the WPAs - reporting error conditions etc.

Also, in my experience - each WPA should be configured to a single hub TEMS... not to both hub TEMS. The reason is that the hub TEMS with the backup role will *not* accept any agent connections. [Actually it does accept a connection and then immediately sends a "go find another TEMS and disconnects".

1) But I cant get WHP MSL's to sync and no situations subscribed to MSL's.
==> What is meant by sync'ing the WHP MSL's. ANd what does "no situations subscribed to MSLs" mean - a sentence fragement it looks like.

2) WHP situations that have agents as distribution target seems to sync just fine though.
==> WHP situations should be distributed only to WPAs, of course.

In any case... WPAs connecting to a hub TEMS should only be configured to that one hub TEMS. I suggest testing that setup out.




Regards,



John Alvord - Ph: 1-720-396-2788    Cell: none
Customer Support - Tivoli Software - jalvord-r/[email protected]<mailto:[email protected]>
Advisory Engineer - Tivoli Monitoring - ITM infrastructure
Follow us on Twitter! @Tivolisupport<http://twitter.com/TivoliSupport> and Facebook<https://www.facebook.com/IBMTivoliSupport>
Personalize your support needs with the IBM Support Portal<http://www.ibm.com/support/electronicsupport/>
Use Service Request<http://www.ibm.com/software/support/servicerequest/quick_start.html> to get assistance!
For emails regarding a PMR, copy [email protected]<mailto:[email protected]>
For secure browser uploads: https://www.ecurep.ibm.com/app/upload
For Customer Support guidance: IBM Software Support Handbook<http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html>

<http://twitter.com/TivoliSupport>






From:        <[email protected]<mailto:[email protected]>>
To:        <[email protected]<mailto:[email protected]>>,
Date:        11/13/2012 06:00 AM
Subject:        [TME10] ITM 6.2.3 FP2 is FTO totally broken?
Sent by:        [email protected]<mailto:[email protected]>
________________________________



Hi all.

Just installed two HTEMS'es with FTO on RHEL6 with 6.2.3 FP02 in our test env.
Both servers are identical with TEMS/TEPS on Derby/WHP all at 6.2.3 FP02. Both TEPS connect locally to each TEMS
Both WHP agents has the primary HTEMS as its primary connection and the secondary HTEMS as secondary, all by the book if you reda the manual.

The FTO "seems" to be working fine switching back and forth when I stop/start the TEMS'esr
But I cant get WHP MSL's to sync and no situations subscribed to MSL's.
WHP situations that have agents as distribution target seems to sync just fine though.

Also tried creating a sit when the secondary was acting HUB, but it never got synced to the other TEMS.

Anyone or is it just me?

/Gus



_______________________________________________
TME10 mailing list
[email protected]<mailto:[email protected]>
Unsubscribe:[email protected]<mailto:[email protected]>

_______________________________________________
TME10 mailing list
[email protected]<mailto:[email protected]>
Unsubscribe:[email protected]
_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]