###BeginCaseStudy###
Case Study: 3
Northwind Traders
Overview
Northwind Traders is an IT services and hosting provider.
Northwind Traders has two main data centers in North America. The data centers are located
in the same city. The data centers connect to each other by using high-bandwidth, low-latency
WAN links. Each data center connects directly to the Internet.
Northwind Traders also has a remote office in Asia that connects to both of the North
American data centers by using a WAN link. The Asian office has 30 multipurpose servers.
Each North American data center contains two separate network segments. One network
segment is used to host the internal servers of Northwind Traders. The other network segment
is used for the hosted customer environments.
Existing Environment
Active Directory
The network contains an Active Directory forest named northwindtraders.com. The forest
contains a single domain. All servers run Windows Server 2012 R2.
Server Environment
The network has the following technologies deployed:
• Service Provider Foundation
• Windows Azure Pack for Windows Server
• System Center 2012 R2 Virtual Machine Manager (VMM)
• An Active Directory Rights Management Services (AD RMS)
cluster
• An Active Directory Certificate Services (AD CS) enterprise
certification authority (CA)
All newly deployed servers will include the following components:
• Dual 10-GbE Remote Direct Memory Access (RDMA)-capable
network adapters
• Dual 1-GbE network adapters
• 128 GB of RAM
Requirements
Business Goals
Northwind Traders will provide hosting services to two customers named Customer1 and
Customer2. The network of each customer is configured as shown in the following table.
Planned Changes
Northwind Traders plans to implement the following changes:
• Deploy System Center 2012 R2 Operations Manager.
• Deploy Windows Server 2012 R2 iSCSI and SMB-based
storage.
• Implement Hyper-V Recovery Manager to protect virtual
machines.
• Deploy a certificate revocation list (CRL) distribution point
(CDP) on the internal network.
• For Customer 1, install server authentication certificates issued
by the CA of Northwind Traders on the virtual machine in the hosting
networks.
General Requirements
Northwind Traders identifies the following requirements:
• Storage traffic must use dedicated adapters.
• All storage and network traffic must be load balanced.
• The amount of network traffic between the internal network
and the hosting network must be minimized.
• The publication of CRLs to CDPs must be automatic.
• Each customer must use dedicated Hyper-V hosts.
• Administrative effort must be minimized, whenever possible.
• All servers and networks must be monitored by using
Operations Manager.
• Anonymous access to internal file shares from the hosting
network must be prohibited.
• All Hyper-V hosts must use Cluster Shared Volume (CSV)
shared storage to host virtual machines.
• All Hyper-V storage and network traffic must remain available
if single network adapter fails.
• The Hyper-V hosts connected to the SMB-based storage must
be able to make use of the RDMA technology.
• The number of servers and ports in the hosting environment to
which the customer has access must be minimized.
Customer1 Requirements
Northwind Traders identifies the following requirements for Customer1:
• Customer1 must use SMB-based storage exclusively.
• Customer1 must use App Controller to manage hosted virtual
machines.
• The virtual machines of Customer1 must be recoverable if a
single data center fails.
• Customer1 must be able to delegate self-service roles in its
hosted environment to its users.
• Customer1 must be able to check for the revocation of
certificates issued by the CA of Northwind Traders.
• The users of Customer1 must be able to obtain use licenses for
documents protected by the AD RMS of Northwind Traders.
• Certificates issued to the virtual machines of Customer1 that
reside on the hosted networks must be renewed automatically.
Customer2 Requirements
Northwind Traders identifies the following requirements for Customer2:
• Customer2 must use iSCSI-based storage exclusively.
• All of the virtual machines of Customer2 must be migrated by
using a SAN transfer.
• None of the metadata from the virtual machines of Customer2
must be stored in Windows Azure.
• The network configuration of the Hyper-V hosts for Customer2
must be controlled by using logical switches.
• The only VMM network port profiles and classifications
allowed by Customer2 must be low-bandwidth, medium-bandwidth, or
high-bandwidth.
• The users at Northwind Traders must be able to obtain use
licenses for documents protected by the AD RMS cluster of
Customer2. Customer2 plans to decommission its AD RMS cluster
during the next year.
###EndCaseStudy###
DRAG DROP
You need to prepare the required Hyper-V virtual network components for Customer2.
Which four objects should you create and configure in sequence? To answer, move the appropriate
objects from the list of objects to the answer area and arrange them in the correct order.
Answer: See the explanation
Explanation:
Box 1:
Box 2:
Box 3:
Box 4:
logical network
uplink port profile
virtual port profile
logical switch
Customer 2 requirement :
“The only VMM network port profiles and classifications allowed by Customer2 must be low-bandwidth, medium-bandwidth, or high-bandwidth”
These port profiles come pre-created on SCVMM.
I believe answer is :
logical network
network site
uplink port profile
logical switch
I’m more inclined to go with this answer. You do not have to ‘create and configure’ any virtual port profiles or classifications since they will be using the default settings anyway.
Agree with movieman
Site:http://m.windowsitpro.com/hyper-v/understanding-hyper-v-networking-system-center-vmm-2012-r2
1. Create the logical networks that relate to your physical networks. (You can also create logical networks for communication isolation purposes.) Create IP pools for the sites you defined in the logical network.
Create the VM networks that relate to sites within the logical networks. Where network virtualization is used, you can create IP pools for the VM subnets to be used for assignment to VMs connected to the virtual networks.
2. Create the uplink port profiles. As mentioned previously, they describe the connectivity between a specific port (which will be assigned later) and the logical networks. This essentially tells VMM which networks a specific NIC on a host can connect to.
Create custom virtual port profiles if needed. VMM provides many virtual port profiles for the various types of traffic, but you can create additional virtual port profiles if needed.
3. Create custom port classifications if needed. Port classifications typically reflect the virtual port profiles. Therefore, if you created additional virtual port profiles, you’ll likely need to create additional port classifications.
4. Create a logical switch. Specify the type of teaming to use, the uplink port profile, the port classifications, and the virtual port profile that relates to each port classification.
Apply the logical switch to a host and select the network adapters on the host to be bound to the logical switch, as shown in Figure 3. You can create additional virtual network adapters for use by the host OS within the possible port classifications that you assigned to the logical switch.
I’d go with OSA, Creation of Port Classification or Port Profiles is not needed as you can use the VMM standards.
Logical Network
Network Site
Uplink Port Profile
Logical Switch
revision:
Create a logical network
Create Uplink Port Profiles
Create Virtual Port Profile
Create Logical Switch..
So movieman was right…
movieman
– logical network
– uplink port profile
– virtual port profile
– logical switch
Martin is right, as he says:
”
It should be:
– a logical network (physical networks)
– a network site (you need to configure IP subnets, there is no DHCP for)
– Create the uplink port profiles. As mentioned previously, they describe the connectivity between a specific port (which will be assigned later) and the logical networks. This essentially tells VMM which networks a specific NIC on a host can connect to.
– a logical switch -> The network configuration of the Hyper-V hosts for Customer2 must be controlled by using logical switches
“
movieman and Hassona are right. I think it’s:
1) A logical network
*** A logical network, together with one or more associated network sites, is a user-defined named grouping of IP subnets, VLANs, or IP subnet/VLAN pairs that is used to organize and simplify network assignments. ***
2) An uplink port profile
*** they describe the connectivity between a specific port (which will be assigned later) and the logical networks. This essentially tells VMM which networks a specific NIC on a host can connect to. ***
3) A virtual port profile
*** this is an optional setting but in this case you really need it to set the bandwidth settings. In the case they ask “The only VMM network port profiles and classifications allowed by Customer2 must be low-bandwidth, medium-bandwidth or high-bandwidth”. ***
4) A logical switch
*** A logical switch brings port profiles, port classifications, and switch extensions together so that you can apply them consistently to network adapters on multiple host systems. In the case they ask “The network configuration of the Hyper-V hosts for Customer2 must be controlled by using logical switches. ***
A network site is not necessary in this case.
https://technet.microsoft.com/en-us/library/jj721568.aspx
https://technet.microsoft.com/en-us/library/gg610588.aspx
https://technet.microsoft.com/en-us/library/jj721570.aspx
https://technet.microsoft.com/en-us/library/dn186234.aspx
https://technet.microsoft.com/en-us/library/jj628166.aspx
https://technet.microsoft.com/en-us/library/jj628155.aspx
http://m.windowsitpro.com/hyper-v/understanding-hyper-v-networking-system-center-vmm-2012-r2
If you are going to use network virtualization, you need a network site
If you want to create static IP address pools that VMM manages, create at least one network site and associate at least one IP subnet with the network site.
If you want to use Dynamic Host Configuration Protocol (DHCP) that is already available on the network to assign IP addresses to virtual devices in a specified VLAN, create network sites with only VLANs assigned to them.
If you want to use DHCP that is already available on the network, and you are not using VLANs, you do not have to create any network sites.
https://technet.microsoft.com/en-us/library/jj721568(v=sc.12).aspx
There is no direct statement in the question that network virtualization is used, but I guess as a hosting provider you need it. This way it doesn’t matter what IP scheme the customers are using. Thet can retain their own IP scheme because you virtualize it.
I was suggested this website by my cousin. I’m not sure whether this post is written by him as nobody else know such detailed about my problem. You are incredible! Thanks!|
i believe these are the appropriate actions and correct order
a logical network
a network site
an uplink port profile
a logical switch
you need to associate an uplink port profile with a network site, then create a logical switch
https://technet.microsoft.com/en-us/library/jj628166(v=sc.12).aspx