Proper sizing of VSS virtual switch link

I am considering using VSS in my collapsed core/distribution on a pair of 6509/Sup2T switches with 6904-40G-2T modules. My closets are 4506/Sup7E, and I have one high-density, mission critical IDF with two fully populated 4510R+E/Sup7E switches. The interlinks will be either 2x or 4x10GE depending on customer decisions to be made. I am trying to find information that would suggest best practice for sizing the VSL. From what I can find, it would appear that not a significant amount of traffic goes across this link if everything in the environment is equally connected to both members of the VSS pairs. So, 2x10GE would be just as good as 4x, or even 2x40GE. However, I haven't found anything definitive yet. Is there a rule of thumb for sizing this link?
Thanks for any guidance.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
The VSL can be the Achilles Heel of a VSS setup.
As you note, if everything is configured optimally, very little traffic should cross this link.
However, suppose a line card fails. As the sup2t supports 80Gbps slot, in theory, that 80Gbps might need to transit the VSL. (NB: Hopefully, VSL also wasn't on the failed card.)
So, to size your VSL, consider bandwidth needs if a line card fails.
Also keep in mind, VSL (at least on 6500s) doesn't allow custom QoS, so you also lose some control on traffic management if VSL congests.

Similar Messages

How to mornitor VSS (Virtual Switching System) & Stack (Switch) By Cisco Prime Infrastructure

Dear all,
I have 02 C6504-E with VSS (Virtual Switching System)
and 02 C3750X-24T-L used Stack
How to you Cisco Prime Infrastructure to monitor VSS & Stack tatus?
Thanks.

Virtual Switching technology is the process of combining two standalone distribution switches found in the local distribution layer into a single management point.
The Virtual Switching System functions and appears as a single switch to the wiring closet and the core layer. You can also create Virtual Switching Systems with a pair of standalone switches available in the core layer.
For configuration please check the below link:
http://www.cisco.com/en/US/docs/net_mgmt/ciscoworks_lan_management_solution/4.1/user/guide/configuration/configvss.html#wp1042960

VSS - Virtual Switch Domain Uniqueness Doubt

Hi everyone,
In the Cisco documentation, says that
You must configure the same virtual switch domain number on both switches of the VSS. The virtual switch domain is a number between 1 and 255, and must be unique for each VSS in your network.
My doubt is how can I understand the word network ?
I cannot use the same Virtual Switch Domain in a L2 Network, in a L3 Network, in a same customer Network ?
For example, if a customer has a lot of sites connected by a MPLS Wan, can I reuse the Virtual Switch Domain in each site ?
Thanks for Advanced
Andre Gustavo

You can re-use the virtual domain ID as long as the the two VSS chassis are not directly connecting to each other. Take a look at this link:
VVirtual Domain
Defining the domain identifier (ID) is the first step in creating a VSS from two physical chassis. A unique domain ID identifies two switches that are intended to be part of the same VSS pair that defines the VSS domain. Assignment of a domain ID allows multiple virtual switch pairs to be connected in a hierarchical manner. Only one VSS pair can participate in a particular domain. The domain ID can have a value ranging from 1 to 255 and must be unique when multiple VSS pairs are connected together. See Figure 2-2.
Figure 2-2 VSS Domain IDs
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/VSS30dg/campusVSS_DG/VSS-dg_ch2.html
Hope this helps!
Thanks you for rating useful posts!

IPS 4270 and VSS (Virtual Switch System)

HI,
I would like to know whether it is possible to connect just One IPS 4270 to a VSS in etherchannel mode (two IPS interfaces per each 6500 Switch).
Thanks in advance

You can re-use the virtual domain ID as long as the the two VSS chassis are not directly connecting to each other. Take a look at this link:
VVirtual Domain
Defining the domain identifier (ID) is the first step in creating a VSS from two physical chassis. A unique domain ID identifies two switches that are intended to be part of the same VSS pair that defines the VSS domain. Assignment of a domain ID allows multiple virtual switch pairs to be connected in a hierarchical manner. Only one VSS pair can participate in a particular domain. The domain ID can have a value ranging from 1 to 255 and must be unique when multiple VSS pairs are connected together. See Figure 2-2.
Figure 2-2 VSS Domain IDs
http://www.cisco.com/c/en/us/td/docs/solutions/Enterprise/Campus/VSS30dg/campusVSS_DG/VSS-dg_ch2.html
Hope this helps!
Thanks you for rating useful posts!

WiSM-2 in 6500 running VSS (Virtual Switching System)

Hi,
Is this SM supported in VSS chassis? I couldn't find information about it. I found only about WiSM-1.
Thanks.

Sup2T 15.0SY VSS config guide add WiSM2 support.
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/15.0SY/configuration/guide/virtual_switching_systems.html
Service Module Support
•Application Control Engine (ACE):
–ACE20-MOD-K9
–ACE30-MOD-K9
•Firewall Services Module (FWSM): WS-SVC-FWM-1-K9
•Network Analysis Module (NAM):
–WS-SVC-NAM-1
–WS-SVC-NAM-2
•Wireless Services Module (WiSM):
–WS-SVC-WISM-1-K9
–WS-SVC-WISM2

Configure Virtual Switch - hyper V - Windows Server 2012R2

On my laptop i have windows server 2012 R2 data center edition installed connected to Wifi. I was able to install and configure to VM's on it. However i am little lost on how to configure the virtual switch for these two VM's. Below are the details:
IP Address : 192.168.1.155
Subnet: 255.255.255.0
Default Gateway: (Blank)
DNS: 192.168.1.254
I do not have any ethernet port, i only have wifi. I did create a virtual switch linked to the NIC (Wifi), and same virtual switch is used by the two VM's. I want few things out of this:
i) I should be able to RDC into both the VM's from other computer when on the same network.
ii) I also want the host and two VM's to be accessible from outside the network.
I need to know what IP addresses should i assign to the virtual switch and each of the VM's. Thanks in advance.

Hi Sqlunlimitedgeek,
The two VMs will need IP addresses on the same range as the host.
Essentially, the switch is like a normal switch and anything connected to it should be able to access each other and the switch itself wont need an IP address.
Just make sure the vSwitch has been configured as an external switch and the "allow management operating system to share this network adapter" is checked. This will create a vEthernet that can be configured on the host with the relevant
IP address and save you exporting out your own via powershell.
The clients all need to be on the same subnet as does the hosts vEthernet.
If your using a team and want to carve that up then powershell is the best way. Especially if configuring a cluster and using a single NIC or Team to created a converged network. In this instance, this doesn't appear necessary as your just using a single WIFI
adapter.
To RDP, just makes sure that is enabled in both VM guests as per normal.
Kind Regards
Michael Coutanche
Blog:
Twitter: LinkedIn:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Configuring and Troubleshooting Virtual Switching System (VSS)

With Anand Ganesan
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about how to monitor, configure, and troubleshoot the Virtual Switching System (VSS) in Cisco Catalyst 6500 Series Switches with expert Anand Ganesan.
VSS is network system virtualization technology that pools multiple Cisco Catalyst 6500 Series Switches into one virtual switch, increasing operational efficiency, boosting nonstop communications, and scaling system bandwidth capacity to 1.4 Tbps. At the initial phase, a VSS will allow two physical Cisco Catalyst 6500 Series Switches to operate as a single logical virtual switch called a virtual switching system 1440 (VSS1440).
For more information, visit: www.cisco.com/en/US/prod/collateral/switches/ps5718/ps9336/prod_qas0900aecd806ed74b.html
The VSS simplifies network configuration and operation by reducing the number of Layer 3 routing neighbors and by providing a loop-free Layer 2 topology.
Anand Ganesan is a customer support engineer in the High-Touch Technical Service team at Cisco specializing in switching protocols. He has been supporting major service providers and enterprise customers in switching and all other switching technologies for more than two years with Cisco. He has a total of eight years of experience in the IT industry. He holds a bachelor of engineering degree from Bharathiyar University, Coimbatore.
Remember to use the rating system to let Anand know if you have received an adequate response.
Because of the volume expected during this event, Anand might not be able to answer every question. Remember that you can continue the conversation in the Network Infrastructure subcommunity, LAN Switching & Routing shortly after the event. This event lasts through September 6, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.

Okay..they are two different /30 networks.
my BFD interfaces are GigabitEthernet1/3/48 and GigabitEthernet2/3/48 and they work fine.
interface GigabitEthernet1/3/48
description Switch 1 BFD Interface
no switchport
ip address 10.48.0.17 255.255.255.252
bfd interval 100 min_rx 100 multiplier 3
end
interface GigabitEthernet2/3/48
description Switch 2 BFD Interface
no switchport
ip address 10.48.0.21 255.255.255.252
bfd interval 100 min_rx 100 multiplier 3
end
switch virtual domain 1
switch mode virtual
switch 1 priority 110
dual-active pair interface GigabitEthernet1/3/48 interface GigabitEthernet2/3/48 bfd
show switch virtual dual-active bfd
Bfd dual-active detection enabled: Yes
Bfd dual-active interface pairs configured:
interface-1 Gi1/3/48 interface-2 Gi2/3/48
router eigrp 1
network 10.0.0.0
network 10.1.201.0 0.0.0.255
network 10.48.0.12 0.0.0.3
network 10.48.177.0 0.0.0.255
network 97.0.0.0
network 99.0.0.0
network 100.0.0.0
network 100.7.7.0 0.0.0.255
network 192.34.145.0
network 192.168.15.0
show ip ei in
EIGRP-IPv4 Interfaces for AS(1)
                       Xmit Queue   Mean   Pacing Time   Multicast   Pending
Interface       Peers Un/Reliable SRTT   Un/Reliable   Flow Timer   Routes
Gi1/2/40           1       0/0         1       0/1           50           0
Gi1/2/41           0       0/0         0       0/1           0           0
Vl1               1       0/0         1       0/1           50           0
Vl7               0       0/0         0       0/1           0           0
Vl13               0       0/0         0       0/1           0           0
Vl15               0       0/0         0       0/1           0           0
Vl21               0       0/0         0       0/1           0           0
Vl25               0       0/0         0       0/1            0           0
Vl26               0       0/0         0       0/1           0           0
Vl134             0       0/0         0       0/1           0           0
Vl135             0       0/0         0       0/1           0           0
Vl140             0       0/0         0       0/1           0           0
Vl300             0       0/0         0       0/1           0           0
Vl400             0       0/0         0       0/1           0           0
Vl199             0       0/0         0       0/1           0           0
Vl6               0       0/0         0       0/1           0           0
Vl20               0       0/0         0       0/1           0           0
Vl24               0        0/0         0       0/1           0           0
Vl30               0       0/0         0       0/1           0           0
Vl31               0       0/0         0       0/1           0           0
Vl37               0       0/0         0       0/1           0           0
Vl2               0       0/0         0       0/1           0           0
Gi1/3/48           0       0/0         0       0/1           0           0
Gi2/3/48           0       0/0         0       0/1           0           0
Vl17               0       0/0         0       0/1           0           0
Gi2/6/40           0       0/0         0       0/1           0           0
Gi2/6/41           0       0/0         0       0/1           0           0
Gi2/1/45           1        0/0         1       0/1           50           0
Gi1/1/33           1       0/0         1       0/1           50           0
My questions revolve around the same point.
Are there any significance in running eigrp or any other routing protocol over this BFD link?
Is the Dual active scenario detected by BFD or BFD notifies a routing protocol like eigrp and in turn dual active is detected?
Should I suppress the eigrp HELLOs on these interfaces to get rid of the log message?
Regards
Vinayak

Virtual Switch adapter getting link-local IP address (apipa)

Hi Everyone,
Not sure what I am doing wrong here.
I have installed an Hyper-V 2012 R2 core server on a brand new Dell server.
I then went to use Virtual Switch Manager via Hyper-V Manager to create a virtual switch adapter, selected external (I want to share my existing server NIC), allow management operating system to share this network adapter.
Then I configured my virtual machine to use this.
When I start the virtual machine I get a 169 type IP address, cannot ping gateway or host. The VM does not even get a proper IP using DHCP. DHCP is working fine from another physical server.
When I check the hyperv core host and select 8 for "Network Settings", I get:
15 192.168.20.44 Broadcom NetXtreme Gigabit Ethernet #5
22 169.254.101.167 Hyper-V Virtual Ethernet Adapter #2
Why is hyperv creating a virtual adapter with an Apipa address which is not usable?
I followed all the steps correctly, but it does not work.
Can anyone point me into the right direction to solve this problem?
Thanks and regards
Ipnotech

This is what IPCONFIG /ALL shows (There is a functonal DHCP server in place):
Windows IP Configuration
   Host Name . . . . . . . . . . . . : cmshyperv1
   Primary Dns Suffix . . . . . . . : newcms.local
   Node Type . . . . . . . . . . . . : Broadcast
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : newcms.local
Ethernet adapter vEthernet (Virtual Switch 1 ):
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter #2
   Physical Address. . . . . . . . . : 00-0A-F7-3E-FD-62
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::6ca4:68e9:a171:65a7%25(Preferred)
   Autoconfiguration IPv4 Address. . : 169.254.101.167(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
   DHCPv6 IAID . . . . . . . . . . . : 855640823
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
   DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
                                       fec0:0:0:ffff::2%1
                                       fec0:0:0:ffff::3%1
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter NIC4:
   Connection-specific DNS Suffix . : newcms.local
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #8
   Physical Address. . . . . . . . . : F8-BC-12-35-A2-8F
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::5daf:241d:7e00:f758%20(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.20.147(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, 2 February 2014 3:44:00 AM
   Lease Expires . . . . . . . . . . : Monday, 10 February 2014 3:43:59 AM
   Default Gateway . . . . . . . . . : 192.168.20.1
   DHCP Server . . . . . . . . . . . : 192.168.20.5
   DHCPv6 IAID . . . . . . . . . . . : 351845394
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
   DNS Servers . . . . . . . . . . . : 192.168.20.5
   Primary WINS Server . . . . . . . : 192.168.20.5
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter NIC3:
   Connection-specific DNS Suffix . : newcms.local
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #7
   Physical Address. . . . . . . . . : F8-BC-12-35-A2-8E
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::91ae:2c7d:ebf3:f71c%19(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.20.138(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, 2 February 2014 3:44:00 AM
   Lease Expires . . . . . . . . . . : Monday, 10 February 2014 3:43:59 AM
   Default Gateway . . . . . . . . . : 192.168.20.1
   DHCP Server . . . . . . . . . . . : 192.168.20.5
   DHCPv6 IAID . . . . . . . . . . . : 335068178
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
   DNS Servers . . . . . . . . . . . : 192.168.20.5
   Primary WINS Server . . . . . . . : 192.168.20.5
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter NIC2:
   Connection-specific DNS Suffix . : newcms.local
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #6
   Physical Address. . . . . . . . . : F8-BC-12-35-A2-8D
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::7cb8:c761:b73:2274%18(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.20.136(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Sunday, 2 February 2014 3:44:00 AM
   Lease Expires . . . . . . . . . . : Monday, 10 February 2014 3:43:59 AM
   Default Gateway . . . . . . . . . : 192.168.20.1
   DHCP Server . . . . . . . . . . . : 192.168.20.5
   DHCPv6 IAID . . . . . . . . . . . : 318290962
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
   DNS Servers . . . . . . . . . . . : 192.168.20.5
   Primary WINS Server . . . . . . . : 192.168.20.5
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter NIC1:
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #5
   Physical Address. . . . . . . . . : F8-BC-12-35-A2-8C
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::3c95:1710:4969:d6d5%17(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.20.44(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.20.1
   DHCPv6 IAID . . . . . . . . . . . : 603503634
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-7E-5F-99-00-0A-F7-3E-FD-62
   DNS Servers . . . . . . . . . . . : 192.168.20.5
   NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter SLOT 2 Port 2:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #4
   Physical Address. . . . . . . . . : 00-0A-F7-3E-FD-61
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Ethernet adapter SLOT 2 Port 4:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #3
   Physical Address. . . . . . . . . : 00-0A-F7-3E-FD-63
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Ethernet adapter SLOT 2 Port 1:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet #2
   Physical Address. . . . . . . . . : 00-0A-F7-3E-FD-60
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.newcms.local:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . : newcms.local
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{CBA3B939-0F6F-40F2-9F1A-4433D5B36865}:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
Tunnel adapter isatap.{DA0EA386-57B7-4441-AB8F-1760F00FD0A6}:
   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #3
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

"Server either does not have a virtual switch configured or none of the configured virtual switches have an IP address assigned" error driving me nuts!

OK; have been trying to setup a test VM based RDS deployment for a few days now with no luck.
this error mentioned above:
"Server <server name> either does not have a virtual switch configured or none of the configured virtual switches have an IP address assigned" error is driving me nuts!
I have removed and re-added the RD Virtualization Host role numerous times, each time having the "create a virtual switch" checkbox selected, but it did NOT create any virtual switch.
I created the external virtual switch manually and tried to create the desktop collection again, no luck with the same error.
a few questions:
1. you don't assign IP to a switch! you assign IP to Network Interfaces. why does the error puts it like this?! it is technically wrong.(yeah yeah I know all about how you'd assign IP to managed switches in real world to telnet into them and manage them.
you know better than me that it is not the case here!)
2.the RDS Virtualization hosts are using their wifi card as the card for the virtual switch. could that be the reason? I even disabled their unplugged wired NIC just to make sure that the wifi is the only available option for the RDS wizard to use for the
virtual switch creation; but it didn't use it and it didn't create any virtual switch automatically.
3.if WIFI nic is indeed the reason, is it your suspension or an official documents is there somewhere stating so (that the WIFI NICS on a Virtualization hosts are not supported as the hub for a virtual switch).
4.what are the properties of the virtual switch the RDS requires? does it have to be external? why can't it work even with my manually created external switch?
5.how would I fix it?
P.S: the environment is made up of 2 laptops, having windows 2012 R2 trial installed on them, using their wifi to connect to the out world. no cable is plugged into their wired NIC card.

Hi,
Thank you for posting in Windows Server Forum.
The simplest short term solution was to connect each computer to a small switch that had no other connectivity. This brought up the link light on the external NIC and allowed the creation of the collection to complete. You need to use an external switch. You
can create one external switch which might fix the problem.
Please check below article for information.
VDI Deployment Error About Virtual Switch
In addition please referthis article for information regarding virtual switch.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Routing of Network Traffic Between VLANs on a Hyper-V Virtual Switch

I am trying to discover how network traffic generated by reads and writes to RDVH User Profile Disks is routed through my network. I have a pool of Hyper-V
desktop vm’s in their own VLAN (vlan1) with their own NIC bound to a Hyper-V Virtual Switch. On the same server I have another management NIC for the OS on a different VLAN (vlan2) and finally on another server I have a virtual machine which hosts the User
Profile Disks. The VM that hosts the User Profile Disks is on the same VLAN as the management NIC for the OS (vlan2).
When tracing the flow of network traffic to and from the User Profile Disk VM it all comes through the vlan2 NIC on the server where the virtual
desktop VMs reside and nothing comes through the vlan1 NIC on this server. I would have expected the traffic to the virtual desktop VMs to come in through the desktop VMs VLAN NIC (vlan1).
This leads me to two possibilities as to how the desktop vm’s on vlan1 get their data to and from the User Pofile Disk vm on vlan2 without routing.
The desktop vm’s Hyper-V Virtual Switch automatically routes the User Profile Disk traffic from vlan1 to vlan2 internally using a virtual switch learning algorithm
Hyper-V itself handles all reads and writes to the User Profile Disks and since that is using the management NIC for the OS it is already on vlan2 and so the network traffic never leaves vlan2.
Any comments on the reason for traffic taking the path it does (as outlined above) as opposed to being layer-3 routed from VLAN1 to VLAN2?

Thanks for your reply Brian. I think your last paragraph above is what I have set up:
If you simply forward one VLAN to one physical NIC and the VMS on the corresponding External Virtual Switch simply end up on that VLAN without Hyper-V doing anything at all - but this dedicats one physical NIC per VLAN.
The Virtual Machines NIC that the vSwitch is patched to and the NIC for the OS are on different VLANS (both NICs are plugged into un-tagged ports on my switch).
The vNICs on the VM's are not tagged to a VLAN (The VLAN ID\ 'Enable virtual LAN identification' box is unticked)
My vSwitch is set up as connected to 'External Network' and isnt shared with the management network.
What I am trying to get at is how would network traffic on the VLAN my vm's are on get to the VLAN that the NIC for the OS is on without going through the router (even though a routable path is available) ?
Is it possible the 'learning algorithm' referneced in a Technet article below is involved here (sorry I cant post links)?
For the virtual machine to communicate with the management operating system, there are two options. One option is to route the network packet through the physical network adapter and out to the physical network, which then returns the packet back to
the server running Hyper-V using the second physical network adapter. Another option is to route the network packet through the virtual network, which is more efficient. The option selected is determined by the virtual network. The virtual network includes
a learning algorithm, which determines the most efficient port to direct traffic to and will send the network packet to that port. Until that determination is made by the virtual network, network packets are sent out to all virtual ports.
Thanks,
Andrew

Virtual switch networking in LDOM error

Hi All,
I am trying to create virtual switches for 10 Gbe interfaces and when I try to bind the resource to the domain, I get the following warning:
root@ebsprdb1 # ldm bind-domain vmprdb1
Mar 11 15:28:54 ebsprdb1 vsw: WARNING: vsw6: Failed to programmacaddr,vid(0:14:4f:f8:23:c5, 0) err=6
Mar 11 15:28:54 ebsprdb1 vsw: WARNING: vsw7: Failed to programmacaddr,vid(0:14:4f:fb:60:5c, 0) err=6
I am able to see the devices in the Guest Domain. Is it safe to ignore the messages?
I used the following commands:
root@ebsprdb1 # dladm show-phys
LINK MEDIA STATE SPEED DUPLEX DEVICE
net1 Ethernet unknown 0 unknown igb1
net0 Ethernet up 1000 full igb0
net3 Ethernet unknown 100 full igb3
net2 Ethernet up 1000 full igb2
net4 Ethernet up 10000 full nxge0
net5 Ethernet unknown 0 unknown nxge1
net6 Ethernet unknown 0 unknown nxge2
net7 Ethernet unknown 0 unknown nxge3
net8 Ethernet up 10000 full nxge4
net9 Ethernet unknown 0 unknown nxge5
net10 Ethernet unknown 0 unknown nxge6
net11 Ethernet unknown 0 unknown nxge7
net27 Ethernet up 1000 full vsw0
net29 Ethernet up 1000 full vsw1
net16 Ethernet up 10000 full vsw2
net33 Ethernet up 10000 full vsw3
net13 Ethernet up 10 full usbecm0
net35 Ethernet up 0 unknown vsw4
net37 Ethernet up 100 full vsw5
root@ebsprdb1 # dladm show-linkprop -p mtu net16
LINK PROPERTY PERM VALUE DEFAULT POSSIBLE
net16 mtu rw 1500 1500 1500
root@ebsprdb1 # dladm show-linkprop -p mtu net33
LINK PROPERTY PERM VALUE DEFAULT POSSIBLE
net33 mtu rw 1500 1500 1500
root@ebsprdb1 # ldm add-vsw net-dev=net16 primary-vsw16 primary
root@ebsprdb1 # ldm add-vsw net-dev=net33 primary-vsw33 primary
root@ebsprdb1 # ldm add-vnet vnet16 primary-vsw16 vmprdb1
root@ebsprdb1 # ldm add-vnet vnet33 primary-vsw33 vmprdb1
Regards

Not sure if you figured this out but at least in my case, tagging the VSW with a VLAN id when the port was already tagged on the switch generated this error. When I recreated the VSW without specifying a VLAN id eliminated the error; all frames leaving the physical switch port will be tagged with its VLAN on egress anyway unless you're using multiple VLANs on the same port.

Server loses internet connection after creating virtual switch in hyper-v

On a fresh Server 2012R2 Essentials install, I set up Hyper-v and created an external virtual switch. Connection to the vm is good but Health Report no shows loss of internet connectivity and that the router is incorrectly setup.
However, I still have a working internet connection? I worry that the server may not update or allow Anywhere Access at some time. Any suggestions? Thanks

If Hyper-V virtual switch behaves strange and server is destined for testing, then it's correct and I recomend delete this virtual switch and create it again.
Here is some issues with internet connection and Hyper-V switch, none of them does not match your problem, but can be inspirative for troubleshooting:
Windows 8 Hyper-V - how to give VM internet access?
Hyper-V kills internet connection when bridging
Configuring Hyper-V for multiple subnets with only one NIC (Server 2008 R2 Edition)
How does basic networking work in Hyper-V?
Best Regards,
thennet

How to route traffic across subnets when one NIC is a hyper-V virtual switch?

Having a bit of a problem with a hyper-V environment which does not seem to route network traffic on two different subnets between each other.
If it were a purely physical server with two NICs and a gateway set traffic would automatically be forwarded between the two different subnets.
However when one of those NICs is a hyper-V virtual switch this simple routing no-longer seems to work and no traffic gets forwarded between subnets?
Situation is:
Hyper-V server with two NICs
NIC 1 = 192.168.0/24 - main Internal company network.
NIC 2 (hyper-V virtual switch.) = 192.168.1/24 - connects to ADSL internet router
Virtualized Domain Controller.
One or two virtualiszed NICs as necessary
How then does traffic get routed between these two subnets? If RRAS has to be configured to do this where is the best place to do it, on the hyper-V host or on the virtualized domain controller?
Thanks,

Hi ,
You can create an internal virtual switch and configure an IP for it (I assume it is 192.168.1.2/24) .
After you enable RRAS in hyper-v host there will be two gateways for different subnets .
" NIC 2 (hyper-V virtual switch.) = 192.168.1/24 - connects to ADSL internet router "
The problem is here ,if these VMs need to access internet .
So , these VMs can not configure their gateway same as the IP of internal virtual switch , you may set VM's gateway as the ADSL internet router's IP meanwhile add a static route entry for every VM .
Please refer to the Syntax :
route add -p 192.168.0.0 mask 255.255.255.0 192.168.1.2
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

How to get the maximum bandwidth/MaxSpeed/Capacity of a Hyper-V virtual-switch?

We are trying to monitor Hyper-V environment (Windows 2008 R2 and Windows 2012) using WMI, and have a very specific question Hyper-V virtual-switch.
We have referred the below mentioned classes and their properties.
1. Win32_NetworkAdapter (namespace:root\cimv2, property:Speed)
2. Msvm_InternalEthernetPort (namespace:Root\virtualization\v2, property: Speed and Maxspeed)
3. Msvm_EthernetSwitchBandwidthData (namespace:Root\virtualization\v2, property:Capacity and Reservation)
All of the above classes and their properties returns 10000000000 (10 GBps) as MaxSpeed, which is NOT correct (as we know that our network connection is of 1 GBps)
Here is our question: How to get the maximum bandwidth/MaxSpeed/Capacity of a Hyper-V virtual-switch?

Until MSFT makes a change to increase the max speed of the virtual switch (and the resulting virtual ports) it will be 10 Gbps.
It has been this way since the original introduction in 2008.
What you are looking for is the most limiting segment in the path. The virtual switch does not assume the properties of the most limiting segment. Since the physical side could be a team, it could be a single NIC.
Your management layer must interpret the most limiting segment.
If you have not already been here:
http://blogs.msdn.com/b/tvoellm/archive/2009/04/23/monitoring-hyper-v-performance.aspx Then take a look.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Windows 8.1 crashes after an extern virtual switch is added

Hello, to get connected from a virtual machine in hyper v I must add an external virtual Switch.
If I do so, after 2 or 3 minutes I get a blue Screen with the message:
Unexpected_kernel_mode_trap.
I have changed the Driver for the Network Card from Intel drive (Intel pro Network Card) to the drive of Microsoft for this Network Card.
I have made 3 Trials with different Drivers for the Network Card.
But allways after some minutes I get the blue Screen mit the message: Unexpected_kernel_mode_trap.
In any case I have to restore the System from a backup, because it is demaged.
Thank you for any help.
Rowe10

Hi，
According to your description, it seems to be hyper v issue. So I suggest that you can post it in technet forum:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/home?forum=winserverhyperv
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Proper sizing of VSS virtual switch link

Similar Messages

Maybe you are looking for