8 Replies Latest reply on Sep 13, 2010 8:09 PM by bshopp

    Cisco 1000v or VMWare vSwitch

    bshopp

      Are you guys out there uses virtual switches?  If you are, are you using the Cisco 1000v or VMWare vSwitch or something else?  What challenges do you face in monitoring and managing virtual switches?

        • Re: Cisco 1000v or VMWare vSwitch
          Questionario

          currently virtual switches, planning to go to nexus.

          currently no monitoring at all for these (dont know how)

            • Re: Cisco 1000v or VMWare vSwitch
              bshopp

              What types of questions would you like answered?  What problems do you face with these switches?  Example, a user cannot see the traffic that goes back forth between hosts on the same vSwitch on the same ESX box.

                • Re: Cisco 1000v or VMWare vSwitch
                  ecornwell

                  We're currently using the VMWare vSwitch but have considered the 1000v.  I would love to get more detail about the networking side of things.  Right now, we monitor the NICs on the ESX servers and then the NICs on the hosts.  We get a little information but we have one Blade Chassis that would be great to monitor in more detail.

                  • Re: Cisco 1000v or VMWare vSwitch
                    kweise

                    I know we've looked at the 1000v but I haven't heard anyone say we're going to them.  We currently have no visibility into the vSwitches on the ESX servers.  You're right, we can't see any host to host traffic for servers on the same ESX box.  We use Opnet products for packet analysis and they make a virtual version of their packet capture appliance we've considered.  However, it's not an issue high on anyone's list right now with budgets being what they are.

                      • Re: Cisco 1000v or VMWare vSwitch
                        bshopp

                        Good discussion.  Let me bubble up the points here

                        1. Monitoring Etherchannels
                        2. Show vNIC to physical adapter mappings
                        3. Collecting statistics from the vNICs
                        4. More native VLAN awareness
                        5. Which port group a specific port is assigned to
                        6. Inter-VM traffic
                        What else do you lack visibility into within the vSwitch or 1000v?  To get visibility into inter-VM traffic, how much would you be willing to pay for that insight?

                  • Re: Cisco 1000v or VMWare vSwitch
                    look4u

                    Our server team is moving away from HP blades and installing Dell servers running VMWare. The first set of these new servers are connected to Cisco 5ks and 2ks.

                    Soon we will be installing 1000v. Previously our biggest concern was limited view into the "vmware" world. Hopefully when the 1000v comes online, we will have better visibility into that environment.

                    I have not researched the NPM capabilities for the 1000v, so will we have a better view inside this virtual world?

                    • Re: Cisco 1000v or VMWare vSwitch
                      bobdawonderweasel

                      We have looked at the v1000 but the same problems exist when monitoring any virtual switch.

                      How much CPU and RAM will monitoring eat up?  Since the vSwitch is nothing more than a piece of software running on a server the VMware host's resources will be used to produce the stats.

                      Bottom line:  A baseline is needed to guesstimate how will monitoring virtual switch stats drag down the performance of the VMware host.

                      • Re: Cisco 1000v or VMWare vSwitch
                        jspanitz

                        Using the vSwitch right now.  Have looked at the 1000v.  There is little visibility into the vSwitch.  1000v seems to solve it at a cost (money & server resources).

                        Right now there is no easy way to tell which pnic a guest is using (we are using etherchannel trunks).  Nor is there a way to see internal traffic or stats on each virtual port.