- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: c-Class VirtualConnect FC *not* using "virtual...
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
тАО06-07-2007 09:35 AM
тАО06-07-2007 09:35 AM
c-Class VirtualConnect FC *not* using "virtual" WWNs
Also, two of the BL480c's are VMware ESX 3.0.1 servers and the WWN's reported in there also don't match what the VC-FC range is supposed to be.
Any suggestions as to what to look for to correct it?
Regards,
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-07-2007 03:36 PM
тАО06-07-2007 03:36 PM
Re: c-Class VirtualConnect FC *not* using "virtual" WWNs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-09-2007 09:22 PM
тАО06-09-2007 09:22 PM
Re: c-Class VirtualConnect FC *not* using "virtual" WWNs
I've also tried re-applying the profile to no apparent effect.
The odd thing is that the WWPN's seem to be /close/ but one or two out when looking at them through the switch management interface. However, it's not as though I think I'm looking at one HBA details but it's actually showing another - the numbers reported in the switch management seem to preceed those within the HBA.
Quite difficult to describe unfortunately :(
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-12-2007 04:46 PM
тАО06-12-2007 04:46 PM
Re: c-Class VirtualConnect FC *not* using "virtual" WWNs
This is by design it would appear. You will notice that the pool for the HBA for the profile with be HBA 1 ends with 011c
and HBA 2 ends with 011e
This is to allow for the PORT and NODE address to be different.
I spent 2 weeks struggling with this. What are you trying to do? I found out how to boot from san with these WWN's off by one.
Email me or post up so we can discuss.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-12-2007 06:06 PM
тАО06-12-2007 06:06 PM
Re: c-Class VirtualConnect FC *not* using "virtual" WWNs
For instance, I was looking at the "1.26" but NOT the "4.00.18" element (latesest is 4.00.85).
All very confusing to a newcommer to "real" SANs - quite a learning curve but good fun too! :)
Based on the wwPn's reported for the PORTs via the VC-FC module, there appears to be an additional virtual wwN for the HBA, one number away from the lowest wwPn (I think, I'm not in the office ATM).
I do want to have a go at boot-from-san once I've finished updating the fw on all the blades so I may well get back to you David.
Thanks both...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2007 06:45 AM
тАО07-05-2007 06:45 AM
Re: c-Class VirtualConnect FC *not* using "virtual" WWNs
thanks
nick
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-05-2007 06:53 PM
тАО07-05-2007 06:53 PM
Re: c-Class VirtualConnect FC *not* using "virtual" WWNs
Go to http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=1844105&prodTypeId=329290&prodSeriesId=1844104&swLang=13&taskId=135&swEnvOID=54 and click on the "Multiboot Image for Qlogic-based c-class FC Mezzanine HBAs" link.
This looks like V 1.26, or even 1.63, but once you've downloaded & installed it, it's actually 1.26 AND 1.63 AND 4.00.85 all in one package!
Regards,
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2007 01:03 AM
тАО07-06-2007 01:03 AM
Re: c-Class VirtualConnect FC *not* using "virtual" WWNs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2007 07:53 AM
тАО07-06-2007 07:53 AM
Re: c-Class VirtualConnect FC *not* using "virtual" WWNs
At the time I had a call logged with HP, eventually they came back to me asking how *I* fixed it as they had another customer with the same issues that they couldn't resolve! I ended up giving them details of what I did to get htings working which they said they'd put into a technical bulleting.
In essence, this is what I had to do to get my (new) EVA4K & San Switch 4/32 setup working:
o Update all firmware
o Have Command View ready to create a new host
o Ensure all zoning is correctly configured (I created a zone for *every* VC-FC WWN within the two VC-FC modules)
o On each blade, boot to the HBA bios and perform a LUN scan for the primary port
o In Command View, create a new host with the newly listed port in the "Ports List"
o Perform the above again on the second HBA port
o Present the appropriate LUNs to the appropriate hosts.
Worked for me...
Regards,
Paul
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-09-2007 06:42 AM
тАО07-09-2007 06:42 AM