Por que o New-SCVirtualNetworkAdapter falha em VMs com nomes com mais de 64 caracteres?

1

Eu tenho 2 VMs idênticas, a primeira tem um nome relativamente curto, enquanto a segunda tem um nome com 65 caracteres. Por que o New-SCVirtualNetworkAdapter é bem-sucedido no primeiro, mas falha no segundo?

New-SCVirtualNetworkAdapter -vm "TestVM_ced7319a-1159-4e8f-bc88-f1487491ef2b"


SlotId                                     : 1
VirtualNetwork                             :
VMwarePortGroup                            :
MACAddressType                             : Dynamic
EthernetAddressType                        : Dynamic
PhysicalAddressType                        : Dynamic
MACAddress                                 :
EthernetAddress                            :
PhysicalAddress                            :
RequiredBandwidth                          : 0
VirtualNetworkAdapterType                  : Emulated
VmwAdapterIndex                            :
LogicalNetwork                             :
VMNetwork                                  :
VMNetworkServiceSetting                    :
VMSubnet                                   :
PortClassification                         :
VirtualNetworkAdapterPortProfileSet        :
LogicalSwitch                              :
GuestIPNetworkVirtualizationUpdatesEnabled : False
MACAddressSpoofingEnabled                  : False
MACAddressesSpoofingEnabled                : False
VMNetworkOptimizationEnabled               : False
VLanEnabled                                : False
VLanID                                     : 0
UsesSriov                                  : False
IsUsedForHostManagement                    : False
VirtualNetworkAdapterComplianceStatus      : Compliant
TemplateNicName                            :
VirtualNetworkAdapterComplianceErrors      : {}
PerfNetworkKBytesRead                      : 0
PerfNetworkKBytesWrite                     : 0
DeviceID                                   : Microsoft:440E7589-D1F4-4C0A-8A9C-B2BCA6305A648032DA-6EFB-4EF4-8152-9A2FBDA945BF
IPv4AddressType                            : Dynamic
IPv6AddressType                            : Dynamic
IPv4Addresses                              : {}
IPv6Addresses                              : {}
PortACL                                    :
ObjectType                                 : VirtualNetworkAdapter
Accessibility                              : Public
Name                                       : TestVM_ced7319a-1159-4e8f-bc88-f1487491ef2b
IsViewOnly                                 : False
Description                                :
AddedTime                                  : 11/26/2015 4:10:45 PM
ModifiedTime                               : 11/26/2015 4:10:48 PM
Enabled                                    : True
MostRecentTask                             : Create network adapter
ServerConnection                           : Microsoft.SystemCenter.VirtualMachineManager.Remoting.ServerConnection
ID                                         : 14f04617-249c-41ab-9d46-3abb9d972238
MarkedForDeletion                          : False
IsFullyCached                              : True
MostRecentTaskIfLocal                      : Create network adapter

New-SCVirtualNetworkAdapter -vm "TestVM_718cdf7b-e4c3-461a-93a8-07f20258c093AAAAAAAAAAAAAAAAAAAAAA"
New-SCVirtualNetworkAdapter : VMM is unable to process one or more of the provided cmdlet parameters. (Error ID: 1600)

Type Get-Help New-SCVirtualNetworkAdapter -full to view a list of defined parameters and complete descriptions. Then
try the operation again.
At line:1 char:1
+ New-SCVirtualNetworkAdapter -vm "TestVM_718cdf7b-e4c3-461a-93a8-07f20258c093AAAA ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ReadError: (:) [New-SCVirtualNetworkAdapter], CarmineException
    + FullyQualifiedErrorId : 1600,Microsoft.SystemCenter.VirtualMachineManager.Cmdlets.NewNICCmdlet
    
por Yonatan 29.11.2015 / 11:03

1 resposta

1

O comprimento do nome da VM no console do System Center Virtual Machine Manager (SCVMM) é limitado a 64 caracteres pela Microsoft. Assim, os commandlets do VMM PowerShell se comportarão como você já experimentou.

    
por 01.12.2015 / 20:49