- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Virtual Connect on a c3000
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
06-17-2011 01:22 AM
06-17-2011 01:22 AM
Virtual Connect on a c3000
I've inherited a c3000 chassis, which came dis-assembled, and I'm having some problems with it. Virtual Connect is not appearing in OA at all, and I can't assign the downlink ports to servers. I'm stumped.
I've assembled it as follows:
Devices:
Bay1: ProLiant BL465c G6
Bay2: StorageWorks SB40c
Bay3: ProLiant BL465c G6
Bay4: Empty
Bay5: Empty
Bay6: Empty
Bay7: ProLiant BL465c G6
Bay8: ProLiant BL465c G6
IB1: Procurve 6120G/XG
IB2: Empty
IB3: Empty
IB4: Empty
I had to put the switch in IB1 as anywhere else, the servers NICs weren't connected.
Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2011 02:06 AM
06-17-2011 02:06 AM
Re: Virtual Connect on a c3000
Unlike a c7000 which have 1 port on IB1 and 2 port on IB2.
Alan
Alan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2011 02:07 AM
06-17-2011 02:07 AM
Re: Virtual Connect on a c3000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2011 02:09 AM
06-17-2011 02:09 AM
Re: Virtual Connect on a c3000
How about the 16 downlinks on the Procurve I have, can I not use them at all?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2011 02:11 AM
06-17-2011 02:11 AM
Re: Virtual Connect on a c3000
Alan
Alan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2011 02:13 AM
06-17-2011 02:13 AM
Re: Virtual Connect on a c3000
Alan
Alan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2011 02:16 AM
06-17-2011 02:16 AM
Re: Virtual Connect on a c3000
If you use a a VC switch (Flex-10) you still limited to connection being stuck on IB1 unless you add mezzanine card. (But you can have upto 8 nics per blade.)
Alan
Alan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2011 02:18 AM - last edited on 07-06-2011 10:13 AM by Kevin_Paul
06-17-2011 02:18 AM - last edited on 07-06-2011 10:13 AM by Kevin_Paul
Re: Virtual Connect on a c3000
Please see this thread. I just answered a similar question on this forum. Might give you some more info.
http://h30499.www3.hp.com/t5/HP-BladeSystem/c3000-mapping-physical-ports-to-blades/m-p/4797542#M13780
Alan
Alan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2011 02:36 AM
06-17-2011 02:36 AM
Re: Virtual Connect on a c3000
First you need to understand that the c3000 enclosure is not designed for redundancy.
Looking downstream from your Procurve switch (or for that matter, from any interconnect module), the 16 downlink ports are HARD-WIRED, 2 ports to each device bay.
Looking upstream from a server blade, the two NICs are hard connected to two ports on the Module in Interconnect Bay 1 (i.e. your Procurve).
If you want to do NIC-Teaming for Network redunancy, you need to put another Procurve in Bay 2, and add an Ethernet Mezzanine card to each Blade on Mezz slot 1.
Treat your Procurve exactly as you would any other switch.
HTH
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-07-2011 09:38 AM
07-07-2011 09:38 AM
Re: Virtual Connect on a c3000
The Procurve 6120G is not a Virtual Connect Module (to the best of my knowledge), and therefore the Virtual Connect Manager link will not appear in the OA navigation window.
The Procurve should be administered as a regular ethernet switch. Use OA, via EBIPA, to assign an IP to the switch, and then you should be able to connect to the switch CLI via telnet or ssh.
HTH
Dave.