- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Port Mapping
BladeSystem - General
1753500
Members
4471
Online
108794
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
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
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
тАО08-14-2007 08:27 AM
тАО08-14-2007 08:27 AM
Hello-
I have two new c7000 enclosures with 12 BL 460c Red Hat Servers in each. Each one has a mezzanine card in the second slot. I also have 6 Vitual Connect Ethernet modules.
I am having a hard time determining what physical ports I need my network folks to plug into.
For instance if I look at the port mappings for say blade 13's 4 mezzanine ports it maps to port 13 in my Virtual Connect modules 5, 6, 7, and 8 but they only have 8 physical ports each. So if I enable eth4 where do I plug in the network connection?
This is probably way easier than I am making it but I appreciate any help!
I have two new c7000 enclosures with 12 BL 460c Red Hat Servers in each. Each one has a mezzanine card in the second slot. I also have 6 Vitual Connect Ethernet modules.
I am having a hard time determining what physical ports I need my network folks to plug into.
For instance if I look at the port mappings for say blade 13's 4 mezzanine ports it maps to port 13 in my Virtual Connect modules 5, 6, 7, and 8 but they only have 8 physical ports each. So if I enable eth4 where do I plug in the network connection?
This is probably way easier than I am making it but I appreciate any help!
He who walks through airport turnstile sideways is going to Bangkok
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 02:29 AM
тАО08-21-2007 02:29 AM
Solution
Hi Romell.
Well, how do you know, there is a port mapping between onboard NICs and mezz slots on blades servers and interconnet devices located on rear of c7000. (you can see that in attached file)
Understanding this mapping, you are be able to know where "eths" are connected.
About the number of physical ports from VC module, 8 ports are confortable and "enough" to connect blades in your network, because you can associate one or all servers that you have with an specific UPLINK in VC module.
For futher information about VC:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00865618/c00865618.pdf
I hope to help you with those information ;)
Salengue
Well, how do you know, there is a port mapping between onboard NICs and mezz slots on blades servers and interconnet devices located on rear of c7000. (you can see that in attached file)
Understanding this mapping, you are be able to know where "eths" are connected.
About the number of physical ports from VC module, 8 ports are confortable and "enough" to connect blades in your network, because you can associate one or all servers that you have with an specific UPLINK in VC module.
For futher information about VC:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00865618/c00865618.pdf
I hope to help you with those information ;)
Salengue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 03:01 AM
тАО08-21-2007 03:01 AM
Re: Port Mapping
Salengue,
I appreciate the help! I played with the vitual connect long enough to figure it out. Part of the problem I was having was that I am new to Red Hat and I was assuming that eth0 would map to bay 1, port 1. The problem was that the first onboard nic was picked up by the OS as eth5 for some reason. I finally found what I needed in the "interconnect bay properties" page in the virtual connect interface. Again thank you for the help!
Romell
I appreciate the help! I played with the vitual connect long enough to figure it out. Part of the problem I was having was that I am new to Red Hat and I was assuming that eth0 would map to bay 1, port 1. The problem was that the first onboard nic was picked up by the OS as eth5 for some reason. I finally found what I needed in the "interconnect bay properties" page in the virtual connect interface. Again thank you for the help!
Romell
He who walks through airport turnstile sideways is going to Bangkok
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-21-2007 04:32 AM
тАО08-21-2007 04:32 AM
Re: Port Mapping
Ohh OK!
I already had the same problem with Linux mapping NICs in a different order as the HW is setted.
Regards,
Salengue
I already had the same problem with Linux mapping NICs in a different order as the HW is setted.
Regards,
Salengue
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