THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
So to overcome this limitation imposed by Hyper-V. we can create some nics to the VPC during the deployment. We can use the extra nics created to support new VPC elements., VPC VR will be deployed with extra nics.
How This is how the deployment for VPC will work when running in Hyper-V.
when the VPC is created, VPC VR will be created on Hyper-V by default with 8 Nics ( 1 public + 1 private + 1 private gateway and 5 extra nics).
first nic will be configure with control IP
Second Nic will be configured with public ip
| type | no of nic used | |
|---|---|---|
| default control ip | 1 | |
| default public ip | 1 | |
| default max tiers | 3 | |
When a new tier/new publicvlan/new private gateway is created on VPC, we will find the free extra nic created and use this nic to configure the associated configuration.
...
when all the extra nics are configured and user attempts to create a new tier etc then exception/error message will be thrown/shown to the user and config will be roll backed.
These extra nics will be used to
it will be we can create some nics to the VPC during the deployment. We can use the extra nics created to support new VPC elements.
Web Services APIs
NA
UI flow
...
Overview
Content Tools
Apps