OCS edge issue

Discussion:

OCS edge issue

(too old to reply)

iann

2008-12-26 15:25:54 UTC

I am having a weird issue with my ocs edge server. Every other day or
so the server stops listening on port 443 and you cannot access office
communicator externally. I have to restart the service and then
everything works fine for a few days and it does it again. It also
seems to happen more often when someone tries to use communicator
mobile. There are no errors in the logs that I can reference so I
can't really troubleshoot it. Internally everything still works when
the external connection does not so its not my internal ocs server. I
would think it maybe the firewally but restarting the ocs access edge
service fixes the issue. Any help would be appreciated.

Mahmoud Magdy

2008-12-28 08:38:09 UTC

Permalink

I have seen such issues on other MS products, Can you tell me the amound of
RAM you are using and HW configuration
--
Regards,
Mahmoud Magdy

Post by iann
I am having a weird issue with my ocs edge server. Every other day or
so the server stops listening on port 443 and you cannot access office
communicator externally. I have to restart the service and then
everything works fine for a few days and it does it again. It also
seems to happen more often when someone tries to use communicator
mobile. There are no errors in the logs that I can reference so I
can't really troubleshoot it. Internally everything still works when
the external connection does not so its not my internal ocs server. I
would think it maybe the firewally but restarting the ocs access edge
service fixes the issue. Any help would be appreciated.

iann

2008-12-28 21:34:53 UTC

Permalink

I doubt it is memory. I am using 16 gigs of memory with a dual quad
core 2.33 ghz processor system. I've also tried changing the port
being used from 443 to 5061 and same result. It's very odd because
there is no consistency to when it happens. It could happen within 2
hrs of restarting the service or 2 days. There seems to be no actual
cause to this issue. I can't see that it is being overloaded
considering only about 15 users are using it.

iann

2008-12-29 21:39:23 UTC

Permalink

I believe I've resolved this issue now. I used wireshark to monitor
the traffic on the edge server and noticed a lot of retransmission
errors. After some troubleshooting it turned out to be the default
gateway setting on the internal interface of the edge server. We
cleared it out and set a static route back to the internal network
through the routing table, which in turn cleared out the
retransmission errors and the service has not stopped working in a few
days now.

Thomas Lee

2009-01-01 13:16:26 UTC

Permalink

In message

Post by iann
I doubt it is memory. I am using 16 gigs of memory with a dual quad
core 2.33 ghz processor system.

I can't recall if Edge is supported on X64, but on i386, you'd only get
4gb of ram. Plus, OCS is an all 32-bit app, thus you only get 4gb of ram
max anyway. How much RAM is OCS using?

Post by iann
I've also tried changing the port
being used from 443 to 5061 and same result. It's very odd because
there is no consistency to when it happens. It could happen within 2
hrs of restarting the service or 2 days. There seems to be no actual
cause to this issue. I can't see that it is being overloaded
considering only about 15 users are using it.

I've seen this on other services. On my home net, DNS just stops working
every couple of days or two - just restaring the service works (for a
while).

Thomas

--
Thomas Lee
(***@psp.co.uk)

iann

2009-01-03 04:16:08 UTC

Permalink

That is correct, it is only utilizing 4 gigs of memory because of
being a 32 bit app but the system was allocated as such so that is
what I used it for. Anyways, the issue is resolved from resetting the
gateway and adding a static route to back to the internal network.

zhang jany

2010-10-10 14:42:30 UTC

Permalink

For the first time feel very honored to visit ,thank you!www.afootwearnews.com

Post by Mahmoud Magdy
I have seen such issues on other MS products, Can you tell me the amound of
RAM you are using and HW configuration
--
Regards,
Mahmoud Magdy

Post by iann
I doubt it is memory. I am using 16 gigs of memory with a dual quad
core 2.33 ghz processor system. I've also tried changing the port
being used from 443 to 5061 and same result. It's very odd because
there is no consistency to when it happens. It could happen within 2
hrs of restarting the service or 2 days. There seems to be no actual
cause to this issue. I can't see that it is being overloaded
considering only about 15 users are using it.

Post by iann
I believe I've resolved this issue now. I used wireshark to monitor
the traffic on the edge server and noticed a lot of retransmission
errors. After some troubleshooting it turned out to be the default
gateway setting on the internal interface of the edge server. We
cleared it out and set a static route back to the internal network
through the routing table, which in turn cleared out the
retransmission errors and the service has not stopped working in a few
days now.

Post by Thomas Lee
In message
I can't recall if Edge is supported on X64, but on i386, you'd only get
4gb of ram. Plus, OCS is an all 32-bit app, thus you only get 4gb of ram
max anyway. How much RAM is OCS using?
I've seen this on other services. On my home net, DNS just stops working
every couple of days or two - just restaring the service works (for a
while).
Thomas
--
Thomas Lee

Post by iann
That is correct, it is only utilizing 4 gigs of memory because of
being a 32 bit app but the system was allocated as such so that is
what I used it for. Anyways, the issue is resolved from resetting the
gateway and adding a static route to back to the internal network.
Submitted via EggHeadCafe - Software Developer Portal of Choice
Review of DevExpress DXperience Control Suite
http://www.eggheadcafe.com/tutorials/aspnet/f8ce82a9-d5c2-44fc-91af-e67df5ae502f/review-of-devexpress-dxperience-control-suite.aspx