
Note If you are planning to configure servers to boot from iSCSI or FCoE, you must create a VNIC
connected to the appropriate iSCSI or FCoE network before proceeding. The Boot settings page will
require you to create the appropriate VNIC before allowing you to set the boot type.
Server Template and Profiles 7-5
Naming Conventions when using Orchestrations
Following points should be considered while using Server Templates in Orchestrations:
• Naming conventions for VM NICs are to be followed. For more information, refer “Naming
conventions for VM NICs” section on page 7-5.
• Server Template Name must not contain spaces.
Naming conventions for VM NICs
For each Server Template created, the names of the VM NICs must match the following names:
• The Server Template for AS50 Hyper-V must use the following VM NIC names:
— nic0
— nic1
— nic2
— nic3
— nic4
— nic5
— nic6
— nic7
• The Server Template for AS50 VMware must use the following VM NIC names:
— vmnic0
— vmnic1
— vmnic2
— vmnic3
— vmnic4
— vmnic5
— vmnic6
— vmnic7
• The Server Template for AS200 Hyper-V must use the following VM NIC names:
— NIC_1
• The Server Template for AS200 VMware must use the following VM NIC names:
— HypervisorManagement
— vMotion
Komentarze do niniejszej Instrukcji