Deployment Proposal
For
Submitted By
Perry Ler
Eguardian Pte Ltd
Deployment Proposal
Content Page
1. Current Network Layout..................................................................................................1
2. Proposed Plan 1................................................................................................................2
3. Proposed Plan 2................................................................................................................3
Version Control
Please document all changes made to this document since initial distribution.
Date Version Author Section Amendment
26/03/2009 1.0 Perry Ler All Initial document creation
Confidentiality of Information
This document contains confidential information of EGUARDIAN Pte Ltd (EGUARDIAN), which is
provided for the sole purpose of permitting the recipient to evaluate the proposal submitted herewith. In
consideration of receipt of this document, the recipient agrees to maintain such information in confidence
and to not reproduce or otherwise disclose this information to any person outside the group directly
responsible for the evaluation of its contents, except that there is no obligation to maintain the
confidentiality of any information which was known to the recipient prior to receipt of such information
from EGUARDIAN, or becomes publicly known through no fault of recipient, or is received without
obligation of confidentiality from a third party owing no obligation of confidentiality to EGUARDIAN.
Deployment Proposal
1. Current Network Layout
Page 1 of 4
Deployment Proposal
2. Proposed Plan 1
Changes to the network design
This plan is to deploy the Link Controller behind the switch. The NAT on the firewall
will be moved to the Link Controller. NAT for the VPN needs to be moved to the Link
Controller as well.
Page 2 of 4
Deployment Proposal
3. Proposed Plan 2
Changes to the network design
This plan is to deploy the Link Controller before the switch. The NAT on the firewall
will be moved to the Link Controller.
Page 3 of 4
Deployment Proposal
4. Information required
1. NAT rules to be transfer from Firewall to Link Controller
2. If plan 2 is preferred by customer, NAT rules need to added for the VPN
3. All the public IPs that Link Controller will handling on behalf.
4. Wide IPs for the load balancing of DNS queries.
5. Internal IPs for the Link Controller
6. External IPs for the Link Controller
Page 4 of 4
Deployment Proposal
4. Information required
1. NAT rules to be transfer from Firewall to Link Controller
2. If plan 2 is preferred by customer, NAT rules need to added for the VPN
3. All the public IPs that Link Controller will handling on behalf.
4. Wide IPs for the load balancing of DNS queries.
5. Internal IPs for the Link Controller
6. External IPs for the Link Controller
Page 4 of 4

F5 Link controller Configuration

  • 1.
  • 2.
    Deployment Proposal Content Page 1.Current Network Layout..................................................................................................1 2. Proposed Plan 1................................................................................................................2 3. Proposed Plan 2................................................................................................................3 Version Control Please document all changes made to this document since initial distribution. Date Version Author Section Amendment 26/03/2009 1.0 Perry Ler All Initial document creation Confidentiality of Information This document contains confidential information of EGUARDIAN Pte Ltd (EGUARDIAN), which is provided for the sole purpose of permitting the recipient to evaluate the proposal submitted herewith. In consideration of receipt of this document, the recipient agrees to maintain such information in confidence and to not reproduce or otherwise disclose this information to any person outside the group directly responsible for the evaluation of its contents, except that there is no obligation to maintain the confidentiality of any information which was known to the recipient prior to receipt of such information from EGUARDIAN, or becomes publicly known through no fault of recipient, or is received without obligation of confidentiality from a third party owing no obligation of confidentiality to EGUARDIAN.
  • 3.
    Deployment Proposal 1. CurrentNetwork Layout Page 1 of 4
  • 4.
    Deployment Proposal 2. ProposedPlan 1 Changes to the network design This plan is to deploy the Link Controller behind the switch. The NAT on the firewall will be moved to the Link Controller. NAT for the VPN needs to be moved to the Link Controller as well. Page 2 of 4
  • 5.
    Deployment Proposal 3. ProposedPlan 2 Changes to the network design This plan is to deploy the Link Controller before the switch. The NAT on the firewall will be moved to the Link Controller. Page 3 of 4
  • 6.
    Deployment Proposal 4. Informationrequired 1. NAT rules to be transfer from Firewall to Link Controller 2. If plan 2 is preferred by customer, NAT rules need to added for the VPN 3. All the public IPs that Link Controller will handling on behalf. 4. Wide IPs for the load balancing of DNS queries. 5. Internal IPs for the Link Controller 6. External IPs for the Link Controller Page 4 of 4
  • 7.
    Deployment Proposal 4. Informationrequired 1. NAT rules to be transfer from Firewall to Link Controller 2. If plan 2 is preferred by customer, NAT rules need to added for the VPN 3. All the public IPs that Link Controller will handling on behalf. 4. Wide IPs for the load balancing of DNS queries. 5. Internal IPs for the Link Controller 6. External IPs for the Link Controller Page 4 of 4