|
|
|
You do not see the port profile/uplink network/network segment on the Microsoft SCVMM server. |
The connection to the Microsoft SCVMM server is down. |
1. Connect to http://VSM-IP to verify that the VSM is reachable from the Microsoft SCVMM server. 2. Launch the Microsoft SCVMM user interface (UI). 3. Choose Fabric Management > Networking > Switch Extension Manager. 4. Refresh the Cisco Nexus 1000V. |
The Microsoft SCVMM server has not pulled the new configuration from the VSM. |
1. Launch the Microsoft SCVMM user interface (UI). 2. Choose Fabric Management > Networking > Switch Extension Manager. 3. Refresh the Cisco Nexus 1000V to force Microsoft SCVMM to pull new configuration from the VSM. 4. Fix any problems with the domain configuration. For information about configuring the domain, see the Cisco Nexus 1000V for Microsoft Hyper-V System Management Configuration Guide . |
The port profile is configured incorrectly. |
1. To verify that publish port profile is configured for the port profile/Network segment/uplink network, enter this command: show network segment name name 2. Fix the port profile using the procedures in the Cisco Nexus 1000V for Microsoft Hyper-V Port Profile Configuration Guide |
An Ethernet interface or vEthernet interface is administratively down. A system message similar to the following is logged:
%VMS-3-DVPG_NICS_MOVED: '1' nics have been moved from port-group 'Access483' to 'Unused_Or_Quarantine_Veth'.
|
A configuration was not saved prior to rebooting the VSM, the configuration was lost, and the interfaces were moved to one of the following port profiles:
- Unused_Or_Quarantine_Uplink
for Ethernet types
- Unused_Or_Quarantine_Veth for vEthernet types
|
1. Verify the port profile to interface mapping by entering the show port-profile virtual usage command. 2. Reassign the VMNIC or PNIC to a nonquarantined port group to enable the interface to be up and forwarding traffic. You must change the port group on the Microsoft SCVMM server. |
After applying a port profile, an online interface is quarantined. A system message similar to the following is logged:
%PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet3/3 has been quarantined due to Cache Overrun
|
The assigned port profile is incorrectly configured. The incorrect command fails when the port profile is applied to an interface. Although a specific command fails, the port profile-to-interface mapping is created. |
1. Identify the command that failed by entering the show accounting log | grep FAILURE command. 2. Verify the port profile-to-interface mapping by entering the show port-profile virtual usage command. 3. Fix the error in the port profile using the procedures in the Cisco Nexus 1000V for Microsoft Hyper-V Port Profile Configuration Guide . 4. Bring the interface out of quarantine by entering the no shutdown command. The interface comes back online. 5. Return shutdown control to the port profile by entering the default shutdown command. |
After modifying a port profile, an assigned offline interface is quarantined. A system message similar to the following is logged:
%PORT-PROFILE-2-INTERFACE_QUARANTINED: Interface Ethernet4/3 has been quarantined due to Cache Overrun
|
The interface has been removed from the DVS. |
To bring the interface back online, see the “Recovering a Quarantined Offline Interface” section. |
A module and all associated interfaces are offline. A system message similar to the following is logged:
2011 Mar 2 22:28:50 n1000v %VEM_MGR-2-VEM_MGR_REMOVE_NO_HB: Removing VEM 3 (heartbeats lost)
2011 Mar 2 22:29:00 n1000v %VEM_MGR-2-MOD_OFFLINE: Module 3 is offline
|
The interface that causes system VLANs for the module has gone down for one of the following reasons:
- System interfaces were removed from the DVS on the Microsoft SCVMM Server.
- The module was powered down.
- There is general loss of connectivity to the module.
|
See the VEM troubleshooting guide to bring the module back online. To bring the interface back online, see the “Recovering a Quarantined Offline Interface” section. |
The interface is in the NoPortProfile state. |
The port profile or uplink networks have been deleted from the VSM but are still on the VMM. If the port profiles are used to attach Ethernet and vEthernet interfaces, the interface will go into the NoPortProfile state. |
1. Check if the GUID of the Ethernet port profile and GUID of the Microsoft SCVMM server uplink port profile set match as follows: a. Display the GUID of the Ethernet port profile by entering the show runing-config port-profile uplinkname command on the VSM. b. Display the GUID of the Microsoft SCVMM server uplink port profile set by entering the PS C:\Program files(x86)\Cisco\Nexus1000V\Support> Get-SCExtensionUplinkPortProfile -name uplinkname command in a PowerShell window. 2. Check if the GUID of the vEthernet port profile matches the GUID of the Microsoft SCVMM server port profile under port classification as follows: a. Display the GUID of the vEthernet port profile by entering the show runing-config port-profile vEthernetName command on the VSM. b. Display the GUID of the Microsoft SCVMM server port profile by entering the PS C:\Program files(x86)\Cisco\Nexus1000V\Support> Get-SCVirtualNetworkAdapterExtensionPortProfile -name vEthernetName command in a PowerShell window. 3. Detach the vEthernet interface from the Microsoft SCVMM server 4. Delete the vEthernet interface manually from the VSM. 5. Refresh the Switch Extension Manager in the Microsoft SCVMM server. 6. Create a new uplink port profile set or a virtual port classification. 7. Attach the original combination of Ethernet and vEthernet interfaces. |
|
In Microsoft SCVMM 2012 you can attach a vEthernet port to a Cisco Nexus 1000V, by using two mandatory parameters VMNetwork and PortClassification. If the PortClassification is not applied, the vEthernet port will go into NoPortProfile state. |
1. In the Microsoft SCVMM UI, use the VM properties to detach the vEthernet/vNIC from the Cisco Nexus 1000V logical switch. 2. Attach the vEthernet/vNIC to the Cisco Nexus 1000V logical switch with both of the parameters. |
The interface is in NoPortProfile and an update failure has occurred at the Microsoft SCVMM UI. |
The vEthernet port profile is a system and the network segment is a nonsystem. This scenario is not supported. |
1. In the Microsoft SCVMM UI, repair the VM and click ignore. 2. Detach the vEthernet interface from the Cisco Nexus 1000V host in the Microsoft SCVMM UI by moving it to a disconnected state. 3. Attach the vEthernet interface back to the Cisco Nexus 1000V by using one of the following supported combinations: – A vEthernet interface that is attached with a system vEthernet port profile and a system network segment. – A vEthernet interface that is attached with a nonsystem vEthernet port profile and a nonsystem network segment – A vEthernet interface that is attached with a nonsystem vEthernet port profile and a system network segment. |
You are unable to add a PVLAN network segment to an uplink port that contains system VLANs. |
If uplink networks are marked as system, the VSM does not allow PVLAN network segment pools. |
1. Remove the system VLAN configuration from the uplink network. 2. Attach the PVLAN network segment pool to the uplink network. 3. Convert the uplink network back to the system. |
You are unable to remove the system keyword from the network segment. |
Sometimes, removing a system keyword is not allowed. |
1. Check if the segment is used by any dynamic profile by entering the show dynamic-port-profile network segment name command. 2. If it is used, delete the dynamic profile. 3. If Step 2 fails, do the following: a. Check if any vEthernet interfaces are using the profile by entering show port-profile name name command. b. If vEthernet interfaces are present, detach the vEthernet interfaces from the Cisco Nexus 1000V by putting the interfaces in the NotConnected state. c. Detach the vEthernet interfaces to move the vEthernet interfaces to a Nonparticipating state so that they can be deleted without any impact. d. After all the vEthernet interfaces are associated with the dynamic port profile are deleted, repeat Step 2. 4. Remove the system keyword from the profile. |
The network segment is not available for attaching to a vEthernet interface. |
A new network segment is associated with an existing network segment pool. However, when you try to attach a vEthernet interface to this new segment, it might not appear the same on the Microsoft SCVMM UI. |
1. Check if the uplink profiles allow the network segment pool that contains the new network segment on the VSM and the Microsoft SCVMM UI. 2. If the segment is missing on the VSM, allow the network segment pool under the uplink network. Refresh the Switch Extension Manager to retrieve the new information. 3. If the segment is missing on the Microsoft SCVMM UI, perform a refresh of the Switch Extension Manager to retrieve the new information. |
VM network not available on Cisco Nexus 1000V. |
The VM network is created on the Microsoft SCVMM but when using this VM network to assign to a VM it fails. |
1. Identify the uplink network of the host where the VM is residing. 2. Verify that the uplink network carries the VM network. 3. Use the appropriate uplink network. |