- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- ESX deployment Cisco 3020 vs Virtual Connect
BladeSystem - General
1752379
Members
6059
Online
108788
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2009 03:47 AM
07-13-2009 03:47 AM
ESX deployment Cisco 3020 vs Virtual Connect
Hello,
We are looking to purchase a C7000 chassis very soon. We have had basic demo's of the Cisco 3020 module and Virtual connect and to be honest I am having trouble working out what the extra cost is about for VC.
I get the whole move the blade and the macs/wwn etc follow it around (Providing its in the domain).
What I do not understand (And this is the only difference I can see) is that VC seems to offer a port mapping scenario (So I could specify a network which comes out of Port 1 + 3 for example, and then allocate this to whatever server NIC's I wanted), can this be done with the Cisco...
Also I am trying to fully understand the benefit of this?
We are looking to purchase a C7000 chassis very soon. We have had basic demo's of the Cisco 3020 module and Virtual connect and to be honest I am having trouble working out what the extra cost is about for VC.
I get the whole move the blade and the macs/wwn etc follow it around (Providing its in the domain).
What I do not understand (And this is the only difference I can see) is that VC seems to offer a port mapping scenario (So I could specify a network which comes out of Port 1 + 3 for example, and then allocate this to whatever server NIC's I wanted), can this be done with the Cisco...
Also I am trying to fully understand the benefit of this?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-13-2009 12:03 PM
07-13-2009 12:03 PM
Re: ESX deployment Cisco 3020 vs Virtual Connect
Yes you can do this with the Cisco, but everytime you add a new blade or wish to change the network config on an existing blade you need to find your expensive Cisco person to do it for you.
With virtual connect its wire once. You get the Cisco person in at the beginning to do a bit more configuration and then you probably do not need them again. As the config can be done in Virtual Connect.
Done properly a VC installation needs a bit extra work upfront from the network/san/server admins but going forward only the server person needs to do ongoing work.
With virtual connect its wire once. You get the Cisco person in at the beginning to do a bit more configuration and then you probably do not need them again. As the config can be done in Virtual Connect.
Done properly a VC installation needs a bit extra work upfront from the network/san/server admins but going forward only the server person needs to do ongoing work.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP