As with NetScaler Cloud Bridge connector connect to another data center

As with NetScaler Cloud Bridge connector connect to another data center -

The CloudBridge Connector feature of Citrix NetScaler appliance connects enterprise datacenters to external clouds and hosting environments.

With it, you can have a Cloudbridge connector tunnel between two different data centers configure to expand your network without reconfiguring it, and the skills of the two data centers use. a Cloudbridge connector tunnel configured between the two geographically separate data centers with permits to implement redundancy and protect the setup of default.

The CloudBridge Connector Tunnel helps to achieve optimum use of infrastructure and resources across two data centers. The applications are available on the two data centers appear as local to the user.

to connect a data center to another data center, put a Cloudbridge connector tunnel between a NetScaler appliance to which are located in a data center and other NetScaler appliance, live in the other data center.

conditions

• One (1) NetScaler MPX or VPX in each data center
• Enable L2 mode on each NetScaler unit
• Enable CloudBridge Connector function
• A (1) Public IP in each data center ready on the NetScaler SNIP in its respective data center
• allow traffic on TCP / UDP ports 50 51 500 and 4500 on the public IP mapped to SNIP respectively in each data center
• machines DC1 should their Gateway as NetScaler in DC1
• machines DC2 should have their gateway as NetScaler in DC2 have

as an example of Cloudbridge connector tunnel between two different data centers, consider an example in which a Cloudbridge connector tunnel between NetScaler appliance up NS_Appliance-1 in the data center DC1 and NetScaler appliance NS_Appliance-2 in data center DC2 .

configuration

• Make sure that layer 2 mode on both NetScaler units activated in DC1 and DC2

• Enable Cloudbridge connector on the NetScaler unit in DC1 and DC2

• on the NetScaler unit in DC1 [1945003Navigieren] to IP tunnel under the Cloudbridge connector section and click in

• in the Create IPv4 tunnel page, fill in the required information

• in the Create IPSec profile page, fill in the required information and click Create [

• back in create IPv4 tunnel page, click create the tunnel Creation

to finish
• Notice how tunnel down is. It remains down until the other NetScaler in DC2 is configured with the tunnel.

• Create a Policy Based Routing (PBR). Navigate to Network> PBRs

• Creating the PBR on your settings

• Note that the PBR is created, but not yet applied

• Take the PBR

• Yes Click the PBR

• Note that the PBR is now activated

apply

• on the NetScaler unit in DC2 Navigate to IP tunnel under the Cloudbridge connector section and click in

• on the page IPv4 tunnel, enter the name, remote

• create the IPSec profile page, the required information, then click create

• When creating on the tunnel side IPv4 back, click create to the tunnel Creation

[terminate

• Notice how tunnel UP is

• Create a Policy Based routing (PBR). Navigate to Network> PBRs

• Creating the PBR on your settings

• Note that the PBR is created, but not yet applied

• Take the PBR

• Yes Click the PBR

• Note that the PBR is now activated

apply

• test from DC1 to DC2 machine machine

Ping from the machine in DC1 172.31.241.20 on a machine in DC2 192.168.1.22 Check the trace route, as it reached to NetScaler in DC1 hops to NetScaler in DC2 and finally his goal

• test of DC2 DC1 machine machine

[1945015onamachineinDC117231240theycheck] Ping from the machine in DC2 192.168.1.22 the trace route, as to NetScaler in DC2 hops then NetScaler in DC1 and finally achieved his goal