Scenario 5: Security Desk outside the corporate network - Security Center 5.9 - 5.10

All about Security Center Federation™

Applies to
Security Center 5.9 - 5.10
Last updated
2021-07-28
Content type
Guides > Administrator guides
Language
English (United States)
Product
Security Center
Version
5.10
5.9

If your Security Desk workstation is outside of the corporate infrastructure on an external network, use this network configuration for Security Center Federation™.

IMPORTANT: The following scenario explains one possible network configuration for Security Center Federation™. Your requirements might differ depending on the number of servers you have, your network specifications, and how you route video.

For more information, see your network administrator or contact Genetec™ Technical Support.

Assumptions about your setup

  • The Federation™ host is federating one remote system on a different network.
  • Both servers are configured to route traffic to a public IP address through a router as follows:
    Federation™ host:
    • Private IP address of the main server: 192.168.100.10
    • Public IP address: 17.5.0.1
    Federated system:
    • Private IP address of the main server: 192.168.1.10
    • Public IP address: 15.65.0.1
  • You are logged on to the Directory of the Federation™ host from a Security Desk workstation that is on an external network at a different location. For example, you are traveling and are connecting to the Directory from an airport or coffee shop.
  • The Media Router and redirector on the federated system are not directly accessible from your Security Desk workstation, so you are receiving video from the redirector on the Federation™ host. You must ensure that the Media Routers and redirectors from both sites can communicate with each other.

Architecture overview

Your system setup looks like this:

Network view on Federation™ host

In this scenario, the networks on the Federation™ host system are configured in the Network view task as follows:

  • The main network for the Federation™ host system is called Network.
  • The main server (VM17272) is part of the main Network. The Properties tab of the Network shows that the main server is routing traffic through public IP address 17.5.0.1 and that it is set up as the proxy server.
  • The federated network (VM16930 - Security Center Federation™) is nested under the main network, and the main network is the only end point configured for the federated video.

Network view on federated system

In this scenario, the networks on the federated system are configured in the Network view task as follows:

  • The main network for the federated system is called Network.
  • The main server (VM16930) is part of the main Network. The Properties tab of the Network shows that the main server is routing traffic through public IP address 15.65.0.1.