| Introduction |
|
6 | (5) |
|
|
|
11 | (5) |
|
|
|
11 | (1) |
|
VLAN concepts and troubleshooting |
|
|
12 | (1) |
|
MAC addresses and virtual guests |
|
|
13 | (1) |
|
|
|
14 | (1) |
|
Example: Intel Teaming NIC driver and VMQ |
|
|
15 | (1) |
|
Monitoring network performance |
|
|
16 | (12) |
|
Physical network adapters |
|
|
21 | (1) |
|
|
|
21 | (1) |
|
|
|
22 | (6) |
|
|
|
28 | (6) |
|
|
|
29 | (1) |
|
|
|
30 | (1) |
|
Diagnostic event log and packet capture |
|
|
30 | (1) |
|
Packet capture within vmswitch |
|
|
31 | (3) |
|
|
|
34 | (4) |
|
|
|
38 | (5) |
|
|
|
39 | (1) |
|
MAC address behavior during live migration |
|
|
40 | (1) |
|
Duplicate MAC addresses on a standalone host |
|
|
41 | (1) |
|
Duplicated MAC addresses due to address range overlapping |
|
|
42 | (1) |
|
Single Root I/O Virtualization |
|
|
43 | (14) |
|
|
|
44 | (2) |
|
|
|
46 | (3) |
|
Enabling the guest operating system |
|
|
49 | (1) |
|
Implementing network redundancy |
|
|
50 | (1) |
|
|
|
51 | (6) |
|
|
|
57 | (9) |
|
Failover cluster networking |
|
|
66 | (4) |
|
|
|
66 | (1) |
|
Network Quality of Service |
|
|
67 | (2) |
|
|
|
69 | (1) |
|
|
|
69 | (1) |
|
|
|
70 | (6) |
|
The new way: Windows Server 2012 cluster network roles and metrics |
|
|
71 | (3) |
|
How SMB Multichannel changes the behavior to select the CSV cluster network |
|
|
74 | (2) |
|
Multitenant networking: Single cluster |
|
|
76 | (6) |
|
Option 1 Consolidated network (single NIC team) |
|
|
77 | (3) |
|
|
|
78 | (1) |
|
Requirement 2 Communication isolation |
|
|
78 | (1) |
|
Requirement 3 Performance |
|
|
79 | (1) |
|
Option 2 Multiple physical networks (many teams) |
|
|
80 | (2) |
|
|
|
80 | (1) |
|
Requirement 2 Communication isolation |
|
|
81 | (1) |
|
Requirement 3 Performance |
|
|
81 | (1) |
|
Multitenant networking: laaS environment |
|
|
82 | (9) |
|
|
|
83 | (1) |
|
|
|
83 | (2) |
|
Layer 2 and Layer 3 isolation |
|
|
85 | (3) |
|
|
|
88 | (3) |
|
|
|
91 | (2) |
|
|
|
93 | (12) |
|
|
|
105 | (20) |
|
Step 1 Check that each virtual machine has the same VirtualSubnetld |
|
|
107 | (1) |
|
Step 2 Check that the lookup records are correct on each host for the virtual machines |
|
|
108 | (1) |
|
Step 3 Check that a WNV subnet gateway address exists on each host for the virtual machines |
|
|
109 | (1) |
|
Step 4 Check that a WNV route exists on each host for each subnet in the virtual machine network |
|
|
110 | (1) |
|
Step 5 Check that each virtual machine's host has the same provider address that was specified in the lookup records |
|
|
110 | (1) |
|
Step 6 Check that the provider routes are correct on each host |
|
|
111 | (1) |
|
Step 7 Check that each host has Network Virtualization bound to a network adapter |
|
|
112 | (1) |
|
|
|
113 | (3) |
|
Use Windows PowerShell to display configuration |
|
|
116 | (3) |
|
Get-NetVirtualizationLookupRecord |
|
|
116 | (1) |
|
Get-NetVirtualizationCustomerRoute |
|
|
117 | (2) |
|
|
|
119 | (2) |
|
Following packets routed through WNV |
|
|
119 | (1) |
|
Troubleshooting dropped packets |
|
|
120 | (1) |
|
Enable debug logging in System Center 2012 VMM SP1 |
|
|
121 | (1) |
|
|
|
122 | (3) |
|
Automating network settings for hosts |
|
|
125 | (5) |
|
|
|
130 | |
|
|
|
130 | (1) |
|
|
|
130 | |
