Answered by:
Supported Edge server topology

Question
-
Hi there,
I have read through the MS deployment guides and this forum, but am still not sure if my intended deployment is supported. Any clarification will be appeciated!
I have a working internal OCS 2007 setup. I have also deployed a single consolidated Edge server. The internal Edge server interface is on the internal network where the OCS front-end sits. The external side of the OCS has only one interface on a DMZ interface which connects to the Internet-facing firewall. The question is -
1. Can I assign all three the edge roles to a single physical interface.
2. Then assign three private DMZ IPs to the single interface, one for each role.
3. Then have three static NATs with three public routable IPs natted to the DMZ IP of each role? This will be configured on the firewall.
So on the firewall the static NAT entries will look like this - (BTW, these are not my real addresses
10.10.10.1 - 194..42.22.1 - AV role
10.10.10.2 - 194..42.22.2 - Access role
10.10.10.3 - 194..42.22.3 - Conference role
I then also have trusted public certs for each role and there is an A-record for each public IP address / server role. Will I have problems with the certs installed on the Edge server reporting their private IPs?
Thanks so long,
Walt.Wednesday, March 26, 2008 10:03 AM
Answers
-
The AV EDGE Server needs a public routeable IP Address so no NAT
The other roles can work with NAT
You can add 3 different addresses and add them to you Physical external NIC
And your internal NIC on the same LAN as OCS FrontEnd is no problem
So everything is fine except for your AV Edge IP that needs to be routeable
Wednesday, March 26, 2008 2:59 PM
All replies
-
The AV EDGE Server needs a public routeable IP Address so no NAT
The other roles can work with NAT
You can add 3 different addresses and add them to you Physical external NIC
And your internal NIC on the same LAN as OCS FrontEnd is no problem
So everything is fine except for your AV Edge IP that needs to be routeable
Wednesday, March 26, 2008 2:59 PM -
Thanks, that is a very clear answer - I have it as above but though IM and Live Meeting works, voice and video does not and I guess it is a result of the AV edge being NATed and breaking the SIP traffic.Wednesday, March 26, 2008 3:47 PM
-
Was it just your *internal* LM video that wasn't working? We are having a problem wereby internal to internal LM sessions cannot start video, but internal to external sessions are working. I suspect it's this routable IP issue but I'm not sure what the easist way to test this would be? I don't admin the servers so I can only make suggestions to those who do.
Tuesday, June 17, 2008 8:37 PM -
I believe for your A/V to work, you need also to have a seperate physical interface for A/V. Have a look at this link:
https://blogs.pointbridge.com/Blogs/schertz_jeff/Pages/Post.aspx?_ID=15
Regards,
Shukri Jarrar
Sunday, July 6, 2008 5:13 PM -
That is just an example and uses NAT for the other EDGE roles
If you don't use NAT 3 public IPs on same Physical NIC with A/V EDGE works perfectly
Tuesday, July 8, 2008 7:02 PM -
Hi Deli Pro-Exchange!
I success publish OCS Access Edge Server by using NAT mechanism. But I cannot publish OCS Web Conference Edge Server by using it. Thanks for any solution!
Thursday, July 10, 2008 2:50 AM -
Are you using correct certificates?
You need a separate A Record in DNS for conferencing and the FQDN must match the common name on the certificate used for Conferencing EDGE
Friday, July 11, 2008 12:12 AM