- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- HP BladeSystem c7000 Virtual COnnect (VC) + Pass-T...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
09-11-2014 08:23 AM
09-11-2014 08:23 AM
HP BladeSystem c7000 Virtual COnnect (VC) + Pass-Thru interconnect modules
Sanyi had a customer question regarding Pass-Thru interconnect modules:
**********
Hello All!
Our customer has very special needs and I need some advice whether it is supported or not.
They have a C7000 chassis. They want to put Virtual Connect modules in the interconnect Bay1 and Bay2 and Pass-Thru modules into the Bay3 and Bay4.
The integrated CNA would communicate with the VC moduls and an additional Mezzazine card would connect to the BAY3-BAY4 Pass-Trhu module.
So basically some connection from the Blade would use the VC uplink and some connection would use the Pass-Trhu modul to reach the external environment.
Is that a supported configuration? To connect from a blade to a Pass-Trhu module do we need to use special Ethernet Mezzazine card or any mezzanine will do the job?
************
Zoltan had a reply:
Hi, we understand that the CNA’s would be not manageable by the VCs, but what can be see about these not VC-paired CNAs from the VC Management?
Do they appear anyhow in the VC (at least inactive/“grayed”) or not at all?
Could somebody shed some light on this?
*************
Input from Dan#1:
They would not show up in VC at all.
*************
Input from Dan#2:
Sometime they show up in VC as being part of the chassis but Not Supported by VC.
I know this is the case for Non VC Switch modules, but not entirely sure on Pass Thrus.
Then in the VC Server Profile you need to account for the way NICs are enumerated and leave blank “Unassigned” entries in the profile for the lines in the profile that equate to Mezz cards attached to Pass Thrus.
If you are not sure, just add a bunch of Unassigned NICs to the Profile (while server is offline obviously) and then assign to the Bay.
Go back into profile and look on the far right at the NIC “Mapping” column.
If you have LOM connected to Flex-10/FlexFabric and Mezz1 is a standard Dual Port NIC, your profile should look like this:
- LOM Port 1 Function A
- LOM Port 2 Function A
- Mezz1 Port 1 Leave “Unassigned”
- Mezz 1 Port 2 Leave “Unassigned”
- LOM Port 1 Function B/C (B if no iSCSI or FCoE. C if you have HW iSCSI or FCoE configured)
- LOM Port 2 Function B/C (same)
- LOM Port 1 Function C/D (etc)
- LOM Port 2 Function C/D (etc)
*************
Reply from Cullen:
That will work fine. Any Ethernet mezzanine will work with passthru.
*************
Other comments or suggestions?