[isalist] Re: TMG Reboot Connectivity Issue
- From: Jim Harrison <Jim@xxxxxxxxxxxx>
- To: "isalist@xxxxxxxxxxxxx" <isalist@xxxxxxxxxxxxx>
- Date: Tue, 24 May 2011 13:28:21 +0000
Is NLB involved at all?
DNS RR?
What's the problem being solved between TMG2 & EMS?
Is it possible that it's exhibiting in a different form for TMG1?
From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On
Behalf Of Jerry Young
Sent: Saturday, May 21, 2011 7:14 AM
To: isalist@xxxxxxxxxxxxx
Subject: [isalist] TMG Reboot Connectivity Issue
All,
I am experiencing this now and it's peculiar. Can anyone explain this
behavior? I'm thinking it's by design but want to understand the reasoning.
I have two array servers, TMG1 and TMG2. I have a separate Enterprise
Management Server (EMS1) acting as the Configuration Storage Server for both
TMG boxes.
Currently, TMG2 cannot communicate with EMS1. I know why and should be able to
resolve that soon. What I don't understand is that in this scenario where TMG1
and TMG2 can communicate but only TMG1 can communicate with EMS1, when one of
those TMG boxes are rebooted, the other TMG box drops off the network like it's
gone into some kind of blocking mode while it is rebooting. When the TMG box
that was rebooted comes back up, everything goes back to being good.
I'd love to understand why. :)
--
Cordially yours,
Jerry G. Young II, CISSP
Microsoft Certified Systems Engineer
Young Consulting & Staffing Services Company - Owner
www.youngcss.com<http://www.youngcss.com>
Other related posts:
