Cisco Cisco Intelligent Automation for Cloud 4.0 技术手册
The Compute POD selected must correspond to one which has the Network POD of the Nexus1kv for the
Datacenter you intend to use. This means the administrator must understand/remember which Network POD
they have associated with the chosen Compute POD. In our cases, selecting the Compute POD which was also
used in the Service Resource Container makes sense. The same Cluster and Datastore were also chosen for
simplicity although any Cluster and Datastore under this Datacenter would suffice.
Datacenter you intend to use. This means the administrator must understand/remember which Network POD
they have associated with the chosen Compute POD. In our cases, selecting the Compute POD which was also
used in the Service Resource Container makes sense. The same Cluster and Datastore were also chosen for
simplicity although any Cluster and Datastore under this Datacenter would suffice.
1.13 Additional Considerations
The data−uplink on the Nexus1kv trunks VLANs out to the fabric (via the physical vmnic) on each of the
ESXi hosts. This needs to be manually configured to pass the specific VLANs of the infrastructure, service,
internet transit and Network POD VLAN range (your subsequent tenant, load balancer and enterprise
networks).
ESXi hosts. This needs to be manually configured to pass the specific VLANs of the infrastructure, service,
internet transit and Network POD VLAN range (your subsequent tenant, load balancer and enterprise
networks).
An example of the uplink is as follows: