...
VmWare Virtual Switch | CS Physical Network | VmWare PortGroup Name | Network | Subnet | Gateway | VLAN TAG | Network Name 1Type | Network IP Range 1Range |
---|---|---|---|---|---|---|---|---|
vSwitch0 | vSwitch0-CS-Dev-MGMT-PN | Management Network | 10.25.243.0 | 255.255.255.0 | 10.25.243.1 | NONE | CS Management | 10.25.243.140 - 10.25.243.146 |
vSwitch0 | vSwitch0-CS-Dev-MGMT-PN | Management Network | 10.25.243.0 | 255.255.255.0 | 10.25.243.1 | NONE | CS Storage | 10.25.243.147 - 10.25.243.149 |
vSwitch2 | vSwitch2-CS-Dev-Public-PN | MGMT | 10.25.243.0 | 255.255.255.0 | 10.25.243.1 | 1045 | Public | 10.25.243.195 - 10.25.243.199 |
vSwitch2 | vSwitch2-CS-Dev-Public-PN | DEV | 10.28.18.0 | 255.255.254.0 | 10.28.18.1 | 1075 | Public | 10.28.19.195 - 10.28.19.199 |
vSwitch2 | vSwitch2-CS-Dev-MGMT-PN | MGMT | 10.25.243.0 | 255.255.255.0 | 10.25.243.1 | 1045 | Guest | 10.25.243.150 - 10.25.243.194 |
vSwitch2 | vSwitch2-CS-Dev-DEV-PN | DEV | 10.28.18.0 | 255.255.254.0 | 10.28.18.1 | 1075 | Guest | 10.28.19.150 - 10.28.19.194 |
You will need administrative VC user and password when configuring vSphere Cluster with CS.
The above table gives you an overview of what I have setup. Please note that while i have listed 6 Physical Network names - we only need to create 4.
vSwitch0-CS-Dev-MGMT-PN, vSwitch2-CS-Dev-Public-PN, vSwitch2-CS-Dev-MGMT-PN and vSwitch2-CS-Dev-DEV-PN.
Moreover, the concept of Public IP space in Advanced Network Shared setup does not apply - as it is meant to be used for internal Non-Isolated network. Therefore, i've allocated a very small amount of public IP space that will be used by CS management VMs only. If you are using Isolated mode, then you should assign more public IP addresses.
Before you begin - you can see my cluster network setup in Virtual Center. I've removed all the remnants of existing CS network setup as i've done this several times before.
This screenshot shows the storage setup - also clean from previous CS storage setup attempts.
Next is to import the System VM image for VmWare.
Login to CS with user that has admin privileges, this screenshot has Citrix CloudPlatform Logo - which is a bug that will be addressed in CS4.0.1
Navigate to Infrastructure > Zones, click add a zoneAdd Zone
Choose Advanced Zone
. .
Complete the required fields for Setup Zone page
When you get to Setup Network, define your Physical Network Names, in my case I created 3 4 Physical Networks - as defined in Network Map above.
Note that I've placed CS Management and Storage Traffic on vSwitch0-CS-Dev-MGMT-PN
The public traffic on vSwitch2-CS-Dev-Public-PN
The Guest traffic for 2 of my VLANs on vSwitch2-CS-Dev-MGMT-PN and vSwitch2-CS-Dev-DEV-PN.
.
.
Illustration above has 3 Physical Networks - as defined in Network Topology Map.
...
Screenshot shows how i've defined 2 Public Networks for DEV and MGMT. This is only required of your are using Isolated Mode in your Network Offering. To make an analogy of what Isolated mode means, look at how AWS does IaaS. They offer an Internal IP address as well as External IP address. If If you are planning to run your environment in traditional manner where NATing is handled by Firewalls, your don't need to define Public Network.
.
I've purposely left VLAN Range blank for both Physical Networks and will do this through API/CLI commands later. This function has not worked as expected through UI interface and Network has not been created.
.
.
.
.
.
.
.
...