Surgient Success

Hi, will look into if we can change that priority.

About "must be access port", do you mean that we can't use trunk ports?

We usually separate customers using different VLAN's using a trunk setup, is this not possible ?

/Jerry

Hi Jerry-

VQMS will use one or two cables from the host server to the physical switch.  There is always one configured as Ezra has described; it is connected to an access port similar to how the Service Console is likely connected.  This is how VMs communicate with the rest of the world.  The second cable, optionally used in NAIL Advanced Mode, is a trunk uplink used to extend the physical switch fabric to the virtual switches of the host.  This is how VMs communicate with each other within a deployed configuration.

During deployment provisioning, VQMS isolates each deployed configuration on one or more VLANs.  This is all managed by VQMS by using the VLAN id resources you created during install and configuration.  In the NAIL Standard Mode, the VLAN segmentation exists only with an isolated switch on the host server.  There is no trunk or uplink cable to the physical switch.  In the NAIL Advanced Mode, the VLAN segmentation spans host servers by leveraging trunk uplinks to the physical switch(es).

Further, to provide external connectivity to the otherwise isolated configurations (e.g. RDP access), NAIL performs NAT on behalf of the deployed VMs.  The NAT external IP address is used on the Default Network (aka VM or VR network).  All external traffic shares the same external VLAN as configured at the physical switch port. (Using a VLAN configured at the port group and a trunk uplink cable may also work depending on if your switch passes STP traffic to the host in this kind of configuration.  Either way, external traffic shares the same VLAN.)

As I have described, NAIL is a mechanism to separate the deployments of individual users.  Separating customers (or organizations of users) within VQMS is a different conversation, if that is what you are after.  VQMS uses the Resource Pooling concept to do this.  By dividing hosts and IP resources into multiple pools, you can separate organizations into multiple logical or physical networks.  But before we get into a potentially lengthy conversation about multiple Pools, lets get your switch configured and your host added to a Pool.  So let us know if you can change the priority of the switch.  If not, as Evan pointed out, these restrictions will change to your benefit when SP1 is released.

-David

Hi, we can't change the priority it seems so that's not an option.

Is there an ETA on when SP1 is coming?

As you may have understood earlier i'm not really interested in separating people from oneanother, more separate customers.

Is there a way through separate pools to simply let each customer/pool have access to a single VLAN and not use any NAIL server at all?

As i see it we don't really benefit from having the NAIL server in place.

The perfect solution for us would be to have the VM's hanging on a regular portgroup on a trunk as any other regular VM.

/Jerry

 Jerry-

 I'll let someone else answer the VLAN isolation issue (not my expertise) but I did want to make sure you understood the function of the NAIL server. NAIL is the mechanism that permits cloned lab isolation -- allowing two cloned labs to run on the same network without MAC or IP conflicts and without requiring changes to lab environments. It is possible that you don't require the NAIL server, if you don't require that level of isolation of a lab, but most customers find they do need it.

Best,
e