how to recover fromTransidle state??

https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1//en_US/Offering_Technical/Technical_Documentation/300-002-940_a04_elccnt_0.pdf

My original post assumes you want to use Transmit idle as an option, the document link provides options to remove or check that you have it properly operational.

Trust this helps

Hi

The point of using SRDF/A Transmit idle is to provide the max level of resilience to any unplanned replication link outages. Transmit idle allows SRDF/A to continue processing during periods of SRDF link disruption. Therefore to want to change it from the transmit option would appear to go against the point of maintaining replication activity to DSE when the link is unexpectedly down. When the link recovers replication across the link will return transferring data retained on DSE.

Others with more direct experience in this will I'm sure provide more details

Thanks all.. !!

hello Allen,

what is the transmit idle time ? 

Hello and Welcome to the Forums!

I'm not sure if I understand your question clearly yet. Are you asking how long Transmit Idle can maintain your groups in async mode during a link outage, or are your referring to something reported while you are in Transmit Idle mode?

For the former, the answer is the same as everything else you could possibly ask... Altogether now everyone: "It Depends" :-)

Honestly though, there are several factors that can have a significant effect on how long you can run in TI mode. The more cache you have in the array the longer you can survive. The lower the Rate of Change on the mirrored devices, the longer you can survive. If you have DSE configured and enabled it will increase your time, and the more capacity allocated to DSE the more you will extend it as well. And finally, the level of activity consuming cache on the rest of the array can have an effect on how much cache is available to TI. There is a cap on the amount of cache to allocate to TI, but that doesn't prevent other processes from using up some of that cache first.

Under the right circumstances we have seen link outages of several hours where we never dropped out of async mode and recovered seamlessly once the link was restored. This was without DSE too. Another factor to consider is that when the cache limit is exceeded you won't immediately drop all your groups (if you have multiples). You will first lose the busiest (based on cache utilization I believe) and those resources will get shared out to keep the rest of the groups running.

If your question was in reference to actually being in TI mode, the TI time reported would be how long you have been in TI mode (not how much time is left). I'm going to go dig and see if I can find where this is reported (assuming I remember correctly as it being available at all).

I hope this helps.

OK, I've confirmed that there is a listing for the current "Transmit Idle Time" in the output from a symrdf query command. It should be on the last line before the detailed listing of the pairs and their states. This will report the current time that TI has been active (which is going to be about 10 seconds less than the actual outage since Transmit idle doesn't kick in until the Link Limbo time expires... this is normally 10 seconds).

it was recovered to async again but am just confused what is 00:00:00 and how it can help in transmit Idle , i checked the documentation i have nothing mentioned about this time ? 

Thanks

Its clear now , thanks

any way to have the old transmitidle statistics ?

Hi ,

ya am asking about this value , its 00:00:00 but what does this means ??

last time link dropped it taked 6hrs and still few groups was in transidle mode ..  so what 0's mean ?

I'm not sure exactly what you mean by that. What exactly are you looking for?

If the group was in TI state this should have shown the time it was in that state (at least that is what I'm seeing in the documentation). I don't have a test system I can try this on to see. If you have confirmed that the group you are querying is definitely still "live" in TI (see the pairs state below that) then you should probably open a case with Support to see if they can help.

That explains why it was showing 00:00:00... under normal operations that is what should be there. This should only change if Transmit Idle is active. Then this will increment to show the time that TI is active. Once the link is restored and you are back to Async mode this will immediately revert to 00:00:00

assume link dropped and Transmit Idle time was 02:02:02 , my link is up now and the group in Async mode , the time will be resseted to 00:00:00 ,,, can i got this information back?? that it took (02:02:02) ?

I don't think you are going to be able to get that directly from SymCLI. I suspect you would have to use something like SPA to look back at the history, assuming the outage was long enough to be recorded. Off the top of my head I'm not sure of another way you could get this info from the array. You would likely have to get it from some other piece of infrastructure involved in the link (e.g. FC switch, link extender, etc.)