Cloud Lab-52: vCloud Director Organizations- “Static Routing between two vApps in Same Organization Routed Network” (Part 2)

This is part 2 of my post regarding Static routing between two vApps in the same organization. lets see what we will cover in “part 2” .

LAB-52 TASKS (Part 2)

In this Lab, we will perform following tasks

  1. Architecture diagram of Static Routing Between two vApps in Same Organization Routed Network
  2. Add Static Routes for vApps 
    • Add Route for “vApp8” Network.
    • Add Route for “vApp2” Network.
  3. Test the vApps communication after Static Routing.

1-Architecture diagram of Static Routing Between two vApps in Same Organization Routed Network

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg1

For sake of domestication. i will allow the communication between two vApps named “vApp2” and “vApp8” respectivelywhich, I already deployed in my Organization “SkyNet” as you can see them in my static routing Architecture diagram.

2-Add Static Routes for vApps.

Navigate to Organization “SkyNet”-> Administration-> Virtual Datacenters -> SkyNet-Dev-OrgVDC-> Org VDC Networks.

Right Click on Network “SkyNet-Dev-OrgRouted” ->Choose “Configure Services”.

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg16

Go to “Static Routing” tab-> Click “Add”

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg21

1-Add Route for “vApp8” Network.

it will allow traffic for vApp8.  In static routing dialog box,  “In Applied on” drop down, choose Organization Network “SkyNet-Dev-OrgRouted”, Enter a descriptive Name “For vApp8” and add route “192.168.16.0/24” Network via “192.168.42.4″ -> Click “OK”

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg22

2-Add Route for “vApp2” Network.

it will allow traffic for vApp2.  In static routing dialog box,  “In Applied on” drop down, choose Organization Network “SkyNet-Dev-OrgRouted”, Enter a descriptive Name “For vApp2” and add route “192.168.15.0/24” Network via “192.168.42.2” -> Click “OK”

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg23

Verify your added routes, it should look like as shown below. Make sure “Enable static Routing” Check box is checked-> Click “OK”

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg24

3-Test the vApps communication after Static Routing

Go to “vApp8-VM1” and open the console and provide the login credentials. once login, because, its linux machine. use “ipconfig”  to check its IP address which is “192.168.16.100”

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg18

If you ping the “vApp2-Web1” VM IP “192.168.15.100”. now we get the reply as shown below.

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg25

Similarly trace the network path of “vApp2-web1” VM. Run tracert 192.168.15.100 on command prompt.

cloudlab52-vCloudOrganization-Staticroutingbatweensameorg26

As you have noticed, we have successfully reached to “192.168.15.100” from our “192.168.16.100” VM. Traffic will pass from “192.168.16.1 (vApp8-VSE Internal IP) -> 192.168.42.1 (SkyNet-Dev-Edge Internal IP) -> 192.168.42.2 (vApp2-VSE External IP) -> 192.168.15.100 (vApp2-Web1 IP)”.

Advertisements

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s