RE: Hub_TEMS FTO Timing

Hey John,
 
Thanks for that information.  Good stuff.  :)
 
Regards,



Gregory R. Mendes
Tivoli Architect/Tools Specialist
Mendes, Inc.
Tivoli Monitoring 6.2.3 Certified
770-317-8593

 
To: [email protected]
Subject: Re: [TME10] Hub_TEMS FTO Timing
From: jalvord-r/[email protected]
Date: Wed, 24 Jul 2013 11:11:45 -0700

On FTO switchover.  I did find a minor
improvement once



FTO Switch Time Speed Up

http://www.ibm.com/support/docview.wss?uid=swg21612077
 



Part of the story is that TEMS heartbeat
is 3 minutes default, but there is a 3 minute hard coded grace period.
There is a second attempt to connect which can be controlled - see technote
involved. Detection of a communications timeout is another factor - also
suppression of new incoming work. There is a reason why the itmcmd server
stop says it may take up to 10 minutes!!



Then there is the problem of the remote
TEMS detecting a loss of hub. That is another series of delays. Some customers
make it worse by listing multiple protocols to get to each hub TEMS



ip.pipe:server1

ip.spipe:server1

ip.pipe:server2

ip.spipe:server2



And if you lose ip.pipe - what do you
think the chances are of having ip.spipe available and working on same
TEMS?



We do not give any estimated time to
switch over... you can see why.  My experience with large environments
is 20-25 minutes is typical.




I suppose you could register the need
with an RFE:



Tivoli Request For Enhancement (RFE)

http://www.ibm.com/support/docview.wss?uid=swg21449404
 [announcement]

http://www.ibm.com/developerworks/rfe/tivoli/
 



There are other High Availability options
besides FTO - HACMP and others. Maybe those would be speedier.



Regards, 

______________________________________________







John
Alvord

Advisory Engineer

IBM Tivoli Monitoring 6 Platform

Customer Support 

Office: 1-720-396-2788 

Mobile: none 

jalvord-r/[email protected]



Cloud
& Smarter Infrastructure
IBM
Support Portal

Open
a New Service Request

Update
your PMR via Email

Escalate
your PMR

My
Blog: Wonderful World of Situations

Secure
upload to ECUREP















From:      
 Gregory Mendes <[email protected]>

To:      
 "[email protected]"
<[email protected]>, 

Date:      
 07/23/2013 12:11 PM

Subject:    
   [TME10] Hub_TEMS
FTO Timing

Sent by:    
   [email protected]








Hello All,

 

Thanks in advance for your answers.  

 

I have a customer that has a 64 second requirement for FTO.  I look
in the "Hot Standby" hub's ms log for "this hub is
now the acting FTO primary".  However, this action is taking
longer than 64 seconds and sometimes 68 - 70 seconds.

 

My question is when does the "Hot Standby" hub actually take
over?  Is it immediately after loosing its heartbeat or when you actually
see, "this hub is now the acting as primary"?

 

Regards,



Gregory R. Mendes

Tivoli Architect/Tools Specialist

Mendes, Inc.

Tivoli Monitoring 6.2.3 Certified

770-317-8593

_______________________________________________

TME10 mailing list

[email protected]

Unsubscribe:[email protected]




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

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