Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

    • 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 new private gateway is created, a nic will be configured with the network vlan id and associated eth device will be configured.
    •  
    • 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.

...