THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
Page History
...
- Existing Negative test cases should pass.
- when services limit reaches 8 and user tries to create any service it will show exception message "Max limit is reached"
Support-ability Characteristics
Logs can be looked up at the following location
- 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".
Use cases
use cases listed in Inter-VLAN Routing
...
So to overcome this limitation imposed by Hyper-V, VPC VR will be deployed with extra nics.
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.
...
| type | supported | no of nic used |
|---|---|---|
| default control ip | 1 | 1 |
| default public ip | 1 | 1 |
| default max tiers | 3 | 3 |
| maximum private gateway | 0-3 | 0-3 |
| maximum new public vlan range | 0-3 | 0-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.
...
Overview
Content Tools
Apps