- 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-11-2010 11:37 PM
тАО09-11-2010 11:37 PM
Then we removed the VC@ Bay2 and removed all profiles and networks and we even did factory reset on VC and Entire Enclosure and unplugged the power cords of enclosure but anytime we define a server profile and assign it to a server at one of server bays, it maps the port LOM2-a to Interconnect Bay 2!!!
Is there any remedy?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-12-2010 10:44 AM
тАО09-12-2010 10:44 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-13-2010 12:20 PM
тАО09-13-2010 12:20 PM
Re: Misbehaviour of Port Mapping on c7000 Blades
This is expected behavior. LOM2 can only leave the enclosure via uplink ports in VC module 1 if there is a module in bay 2 as well.
good luck
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2010 02:04 AM
тАО09-14-2010 02:04 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
eth0->LOM1-a Bay#1
eth1->LOM2-a Bay#1
After Inserting the Second module, the mapping became like this:
eth0->LOM1-a Bay#1
eth1->LOM1-a Bay#2
Then, I removed the Second VC Module, Performed a factory reset and unplugged the enclosure power-cord and plugged it again!
But The Mapping still is:
eth0->LOM1-a Bay#1
eth1->LOM1-a Bay#2
The VC@Bay#2 no longer exists! This would not be hard-wired mapping policy for this case, since the initial hard-wired policy before inserting the second module was:
eth0->LOM1-a Bay#1
eth1->LOM2-a Bay#1
I am just looking for a workaround!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2010 06:30 AM
тАО09-14-2010 06:30 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
You can leave the virtual network for LOM2-a (as well as LOM2-b,c,d) set to Unassigned. That way you can continue to add flex adapters on LOM1.
No trouble doing this, and it allows you to add the VC module in bay 2 at a later date if you choose.
good luck, if you appreciate the answers we appreciate the points!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-14-2010 07:13 AM
тАО09-14-2010 07:13 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2010 01:49 AM
тАО09-15-2010 01:49 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
eth0->LOM1-a Bay#1
eth1->LOM2-a Bay#2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2010 01:15 PM
тАО09-15-2010 01:15 PM
Re: Misbehaviour of Port Mapping on c7000 Blades
> before inserting the second VC module, for each server was like this:
> eth0->LOM1-a Bay#1
> eth1->LOM2-a Bay#1
If eth1 == LOM2, then it is simply not possible for it to map to Bay #1. The mapping is HARD, and immutable. LOM#2 maps to Interconnect bay #2, there is nothing you can do about it.
You need to pay attention to David, he knows a bit about this stuff.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-15-2010 11:28 PM
тАО09-15-2010 11:28 PM
Re: Misbehaviour of Port Mapping on c7000 Blades
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-16-2010 12:59 AM
тАО09-16-2010 12:59 AM
Re: Misbehaviour of Port Mapping on c7000 Blades
THIS is not what I THINK, this is What I SEE!