- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- The rule to make FCoE FlexHBA WWN
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
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
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
11-25-2014 10:50 AM
11-25-2014 10:50 AM
The rule to make FCoE FlexHBA WWN
Dae Yong had a question regarding FCoE World-Wide Names (WWN)
*************
Hello experts,
Simple question about VC Flexfabric.
When configured by vc-defined for ethernet and factory-defined for fc, what is the rule(combination) to make FCoE FlexHBA WWN?
It seems that vc-defined mac address is used to make it.
************
Input from Fred:
Yes, VCM uses the VC-assigned MAC address to generated the WWN in this case. This behavior has its roots in older versions of OA which didn’t provide the actual hardware FCoE WWPNs to VCM.
Newer versions of OA now provide the actual hardware FCoE WWPNs and HP OneView will use them as part of its FCoE support.
Question back from Dae Yong:
Fred, thanks for good information. I understand that FCoE WWN is generated by VCM (but, it’s NOT VC-defined), even though it’s defined as factory-default.
What is older version of OA? ex. older than FW 4.00. And IF update to newer version of OA, can FCoE WWPNs be changed to actual one without notice or warning?
Please help me more.
Reply from Fred:
This addressing algorithm will continue unchanged in VCM. Updating OA or VC will have no effect on existing addresses.
***************
Comments?