locked
Virtual Edge server RRS feed

  • Question

  • Hi,

    I have deployed my OCS 2007 in my lab test. My lab test is behind a Firewall and a Nat router (when i go on internet my public ip is 194.. and my priv. is 10.10...)

    I have deployed on physical machine:

    - OCS 2007

    - Mediation 

    - 2 OC 2007 clients.

    But... i have no enough computer to install EDGE server.. !

    So.. I have a vitual edge server (.vhd file), but i don't know if it is possible to connect this virtual edge server to the rest of my network/domain... ?

    If yes, how i can configure so that the router forwards packets on the private ip of the edge server?

    Regards,

    Thursday, October 9, 2008 4:53 PM

All replies

  • Hi,

     

    The easiest deployment for your EDGE server would be to assign 2 virtual network interfaces to the virtual machine. One that would connect to the public facing network and the other that would connect to your internal facing network.

    This requires that your physical machine hosting the EDGE server would have 2 physical interfaces as each virtual network interface has to bind to a physical interface.

     

    I don't know about your Firewall/NAT router but mine has a DMZ port on it which basically allows me to put a host on the internet without NAT which is good because then you get to least amount of issues as OCS requries a public IP directly routable without NAT to ensure that STUN (or Simple Traversal over UDP and NAT) works.

     

    So assuming you have a DMZ port on your router this is where the physical interface that binds to the external facing virtual interface of my EDGE machine would connect to. The other physical interface would go into a regular switch that connects up to the other OCS Servers.

     

    I hope this is somewhat clear :-)

     

    Sincerely,

    Tonino Bruno

     

     

    Thursday, October 9, 2008 7:57 PM
  • Hi,

    the requirement to have public IP address (not NATed) is valid only for the A/V edge role, all the rest of the edge roles can have IP addresses from the internal addressing scope and those can be then translated to public ones.

    It is recommended to have multiple network adapters to support multiple edge roles.

    Regards,
    Michal
    Wednesday, October 29, 2008 6:49 PM