- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Virtual Connect is not forcing the WWN's
BladeSystem - General
1753767
Members
5685
Online
108799
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
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
тАО10-01-2009 07:00 AM
тАО10-01-2009 07:00 AM
Virtual Connect is not forcing the WWN's
Hi,
I have a weird issue where blades in a particular enclosure are showing up on the SAN using their default (burned in) WWN rather than the VC assigned one. Within VC and OA the blades are associated with the VC assigned WWN, but when looking from the fabric the default WWN is seen.
I have numerous other enclosures all with the same config and they are presenting on the SAN correctly.
Does anyone have any ideas why this may happen?
I am running;
-> VC - 2.10
-> OA - 2.51
-> Blade BL685c G1 (A08 01/29/2009)
-> iLO - 1.78
-> HBA (Emulex LPe1105-HP) FW - 2.72a2
It is a Brocade fabric and the switches are running the latest code and all configured identically, and as I say other blade enclosures/servers are appearing with the correct WWN's.
I have already deleted all profiles and re-created.
Like I say, any ideas?
Thanks
Kevin
I have a weird issue where blades in a particular enclosure are showing up on the SAN using their default (burned in) WWN rather than the VC assigned one. Within VC and OA the blades are associated with the VC assigned WWN, but when looking from the fabric the default WWN is seen.
I have numerous other enclosures all with the same config and they are presenting on the SAN correctly.
Does anyone have any ideas why this may happen?
I am running;
-> VC - 2.10
-> OA - 2.51
-> Blade BL685c G1 (A08 01/29/2009)
-> iLO - 1.78
-> HBA (Emulex LPe1105-HP) FW - 2.72a2
It is a Brocade fabric and the switches are running the latest code and all configured identically, and as I say other blade enclosures/servers are appearing with the correct WWN's.
I have already deleted all profiles and re-created.
Like I say, any ideas?
Thanks
Kevin
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-01-2009 12:04 PM
тАО10-01-2009 12:04 PM
Re: Virtual Connect is not forcing the WWN's
Only time I have ever seen this is when the HBA Firmware is out of date. Not the case here.
is your HBA BIOS version showing as 4.00a6?
and the fact that it is happening to the entire enclosure makes it seem like it's not an HBA issue. What is your VC FC Module Firmware? Try resetting the VC-FC modules? Try resetting the OA modules?
Are you sure its the factory WWN you're seeing and not VC FC's own WWN?
is your HBA BIOS version showing as 4.00a6?
and the fact that it is happening to the entire enclosure makes it seem like it's not an HBA issue. What is your VC FC Module Firmware? Try resetting the VC-FC modules? Try resetting the OA modules?
Are you sure its the factory WWN you're seeing and not VC FC's own WWN?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-02-2009 12:26 AM
тАО10-02-2009 12:26 AM
Re: Virtual Connect is not forcing the WWN's
Have you set the Virtual WWPN to be ones from a VC pool or to reuse the ones on the HBAs. If its the latter and you have not moved any profiles...then what you have is what I would expect to see.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-04-2009 06:59 PM
тАО10-04-2009 06:59 PM
Re: Virtual Connect is not forcing the WWN's
Are you still having this problem? There are a number of possible causes for physical pWWN to show instead of the expected virtual addresses with Virtual Connect FC.
Contact the HP SAN Switch support team and provide the OA inventory report (Show All) and at least one of the SAN switch support logs.
terri.harris@hp.com
Contact the HP SAN Switch support team and provide the OA inventory report (Show All) and at least one of the SAN switch support logs.
terri.harris@hp.com
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