Scenario 1:7 – Private Networks (Simple vNet) 90
Figure 1-80
Private VLANs - Simple Network Connection showing a single Ethernet uplink to a single VC-Enet port
(Port 1). VC-Enet Port 1 is configured as part of the VC Network Prod-Net. As the Private Network feature is enabled
on Prod-Net, servers that are connected to Prod-Net will not be able to talk directly to each other within VC, an external
router would be required. “Prod-Net” is presented to Server Profiles Web-1 through Web-4. Each profile is applied to
bays 1-4 respectively
.
Installation and configuration
Switch Configuration
Appendices A and B provide a summary of the commands required to configure the switch in either a
Cisco IOS or a ProCurve network infrastructure. The configuration information provided in the appendices
assumes the following information:
•
The switch ports are configured as ACCESS ports, either presenting the Default VLAN or a specific
VLAN and will for forwarding untagged frames.
VC CLI commands
Many of the configuration settings within VC can also be accomplished via a CLI command set. In order to
connect to VC via a CLI, open an SSH connection to the IP address of the active VCM. Once logged in,
VC provides a CLI with help menus. Through this scenario the CLI commands to configure VC for each
setting will also be provided.
Configuring the VC module
•
Physically connect Ports 1 and 2 of the first network switch to Ports 1 and 2 on the VC module in Bay
1.
•
Physically connect Ports 1 and 2 of the second network switch to Ports 1 and 2 of the VC module in
Bay 2, if you have only one network switch, connect the second VC module cables to alternates port
on the same switch. This will NOT create a network loop and does not require Spanning Tree to be
configured.
