Discussion:
OCS Edge Nic Config Question
(too old to reply)
Thomas Oeser
2009-02-25 10:13:51 UTC
Permalink
Hello,

we have OCS 2007 R2 Standard Front End Deployed and now want to setup the
edge server.

We have a true DMZ, so the Edge Server is covered by 2 watchguard firewalls,
one to external and one to internal. The Edge Server is in between.

On the Edge Server we have 4 NICs.

For each edge role we have one nic with a DMZ-IP, we can not assign public
ips.

So we have:

10.110.1.5 Subnetmask 255.255.255.128-->Access Edge
10.110.1.6 Subnetmask 255.255.255.128-->WEbconf
10.110.1.7 Subnetmask 255.255.255.128-->A/V

In addition the last nic should communicate with our front end server and
has the following ip:

10.110.1.250 Subnetmask 255.255.255.128


Our internal network is 10.105.105.x

So what about default gateway? Where to define that? What about
communication to internal network? Static Route?
Russ Kaufmann
2009-02-25 14:41:25 UTC
Permalink
Post by Thomas Oeser
Hello,
we have OCS 2007 R2 Standard Front End Deployed and now want to setup the
edge server.
We have a true DMZ, so the Edge Server is covered by 2 watchguard firewalls,
one to external and one to internal. The Edge Server is in between.
On the Edge Server we have 4 NICs.
For each edge role we have one nic with a DMZ-IP, we can not assign public
ips.
10.110.1.5 Subnetmask 255.255.255.128-->Access Edge
10.110.1.6 Subnetmask 255.255.255.128-->WEbconf
10.110.1.7 Subnetmask 255.255.255.128-->A/V
In addition the last nic should communicate with our front end server and
10.110.1.250 Subnetmask 255.255.255.128
Our internal network is 10.105.105.x
So what about default gateway? Where to define that? What about
communication to internal network? Static Route?
Default GW should be on the 10.110.1.x network and pointing to the external
fw. The rest of the routing should be automatically generated but you might
have to create the route for the 10.105.105.x network that points to the
internal fw as the gateway for the internal address space.
Thomas Oeser
2009-02-25 19:56:30 UTC
Permalink
Thank you Russ, helped me out.
Post by Russ Kaufmann
Post by Thomas Oeser
Hello,
we have OCS 2007 R2 Standard Front End Deployed and now want to setup the
edge server.
We have a true DMZ, so the Edge Server is covered by 2 watchguard firewalls,
one to external and one to internal. The Edge Server is in between.
On the Edge Server we have 4 NICs.
For each edge role we have one nic with a DMZ-IP, we can not assign public
ips.
10.110.1.5 Subnetmask 255.255.255.128-->Access Edge
10.110.1.6 Subnetmask 255.255.255.128-->WEbconf
10.110.1.7 Subnetmask 255.255.255.128-->A/V
In addition the last nic should communicate with our front end server and
10.110.1.250 Subnetmask 255.255.255.128
Our internal network is 10.105.105.x
So what about default gateway? Where to define that? What about
communication to internal network? Static Route?
Default GW should be on the 10.110.1.x network and pointing to the
external fw. The rest of the routing should be automatically generated but
you might have to create the route for the 10.105.105.x network that
points to the internal fw as the gateway for the internal address space.
Loading...