Scenario 1:7 – Private Networks (Simple vNet) 88
Scenario 1:7 – Private Networks (Simple vNet)
Overview
This scenario uses the private Networks feature to restrict communications between hosts within a Virtual
Connect Network. In this scenario, a single uplink port from the VC module will be used to carry a single
or multiple VLANs to a simple vNet. The vNet is configured with the Private Networks feature enabled.
The adjacent hosts within the vNet will not be able to talk to other servers within the VC Domain, even if
on the same VLAN, and an external router would be required.
This configuration uses the Virtual Connect vNet. The vNet is the simplest way to connect Virtual Connect
to a network and server. In this scenario, the upstream network switch connects a network to a single port
on each VC module.
No special upstream switch configuration is required as the switch is in the factory default configuration.
Requirements
In order to implement this scenario, an HP BladeSystem c7000 enclosure with one of more server blades
and TWO Virtual Connect Ethernet modules, installed in Bays 1& 2 are required. In addition, we will
require ONE or TWO external Network switches. As Virtual Connect does not appear to the network as
a switch and is transparent to the network, any standard managed switch will work with Virtual Connect.
Depending how we assign the VC networks to the servers, will determine whether the VC-Enet module will
simply pass these VLANs through and not interpret the VLAN tag, in which case the VLAN tag will be
interpreted by the OS on the assigned blade. Or an individual VLAN could be assigned to a server NIC,
in which case, VC could interpret the VLAN tag and then forward the untagged frame to the server NIC.
