- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: Misbehaviour of Port Mapping on c7000 Blades
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
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
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-16-2010 02:47 AM
тАО09-16-2010 02:47 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
All I can say is that this column is not configurable to the best of my knowledge. So what you see is a genuine issue.
I rechecked all of my profiles, and in every case LOM1 and LOM3 map to Bay 1, and LOM2 and LOM4 map to Bay 2, which is how the mapping is supposed to look.
There certainly seems to be something screwy about this setup.
If this mapping is being put into every profile you create, then my suggestion would be to restart the whole VC configuration from scratch. This would entail shutting down all of your servers, removing the VC module in Bay 2, and delete the domain.
Then remove and reinsert the module in Bay 1.
Log in to VC on Bay 1 (need default User/Password).
Import the domain.
Rebuild the VC configuration from scratch, (don't import a saved config).
We had to do a similar process when upgrading from 1/10G VC's to Flex10 VC's. We found that importing the config from the 1/10G modules reversed the mappings.
Different issue to yours, but enough similarities to make it worth your trying it, (if no other option is available)
And of course, you can save your current configuration so that if the rebuild fails, you can get back to where you are now.
Good Luck
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2010 02:58 AM
тАО09-16-2010 02:58 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
eth0->LOM1-a Bay#1
eth1->LOM2-a Bay#2
This is actually the correct mapping, and is probably why it is defaulting to this in all of your profiles.
Dave.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2010 12:10 AM
тАО09-23-2010 12:10 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2010 06:28 AM
тАО09-23-2010 06:28 AM
SolutionMezz2 cards on a c3000 should be mapped to IC Bays 3 & 4.
For dual port cards - Pt1 -> Bay 3 and Pt2 -> Bay 4.
For Quad port cards - Pt1 & Pt3 -> Bay 3, and Pt2 & Pt4 -> Bay 4.
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-24-2010 10:07 PM
тАО09-24-2010 10:07 PM
Re: Misbehaviour of Port Mapping on c7000 Blades
- « Previous
-
- 1
- 2
- Next »