Page History

...

• • Only max of 7 vpc Entities are supported because Hyper-V supports only 8 virtual network adapters to VM (http://technet.microsoft.com/en-us/library/jj680093.aspx)
  • VPC VR will be created with 8 nics up front.
  • when VPC is created successfully, vpc vr should be created in Hyper-v and one nic will be configured with control ip and second nic will be configured with public ip.
  • when new tier is created, a nic will be configured with the network vlan id and associated eth device will be configured.
  • when a tier is deleted associated nic will be un configured and associated eth device will be configured to be down state.
  • when new private gateway is created, a nic will be configured with the network vlan id and associated eth device will be configured.
  • when a private gateway is deleted associated nic will be un configured and associated eth device will be configured to be down state.
  • when public ip is acquired and configured from a new vlan range,  a nic will be configured with the network vlan id and associated eth device will be configured.
  • when last public ip from a vlan range is released associated nic will be un configured and associated eth device will be configured to be down state.
  • When new entity is created and fails to configure the virtual nic, then "Fail to hot plug Nic" error will be shown
  • When a tier/private gateway has to be created, if there is an error while modifying the VPC VR Nic, then the command will be failed and database changes will be roll-backed.
  • When a tier/private gateway got created successfully, then the vlan specified by the CS will be assigned on the NIC and internally associated eth device will be configured and will be in "UP" state.
  • When a tier/private gateway got removed successfully, then vlan will be removed on the VR NIC and associated eth device will be configured to  "down" state.
  • Add Vm to another other tiers in the VPC .will work if the VM is in stopped state and max to  8 tiers due to Hyper-V Virtual Network Adapter limitation
  • 
    

Negative

• • When entity limit reaches 7 and user tries to create any service it will show exception message "Max limit is reached"entity, plugnic command will be failed with plugnic failure exception message to add vpc entity and reason will be logged "Plug Nic failed for the vm as it has reached max limit" 

Support-ability Characteristics

...

• • Management server logs for VPC commands will be logged in management-server.log and vmops.log(dev setup). All the requests forwarded to the Hyper-V agent can also be seen here.
  • The Hyper-V agent logs can be seen in windows event viewer on the respective hosts. The logs can be filtered by source "CloudStack Hyper-V Agent".
  • Hyper-V specific logs can be viewed in the event viewer under "Application and Services Logs" >> Microsoft >> Windows >> "Hyper-V-VMMS".
  • Vpc manager will log the vpc entities management in the management server.
  • ModifyVmNic agent command operations log will be present in management server log and in hyperv agent log when vpc entities were managed.
  • PlugNic/UnplugNic commands operations log will be present in management server log and in hyperv agent log when vpc entities were managed. 

Supported Hypervisor

This feature is implemented for Windows Server 2012 R2 and Hyper-V 2012 R2 (Core).

...

When all the extra nics are configured/used and user/admin attempts to create a new tier etc then exception/error message will be thrown/shown to the user and config will be roll backedany new vpc entity then  plugnic command will be failed with plugnic failure exception message to add vpc entity and reason will be logged "Plug Nic failed for the vm as it has reached max limit".

Web Services APIs

No new web apis were added

...