- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Fibre Channel Virtual Connect - blades not seeing ...
BladeSystem - General
1752766
Members
5028
Online
108789
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
тАО12-16-2007 10:09 AM
тАО12-16-2007 10:09 AM
Fibre Channel Virtual Connect - blades not seeing SAN
I've got a c7000 chasis with the 4GB fibre channel virtual connect module, DL465c blades with QLogic mezzanine cards. All of these are on the latest firmware.
I have a Cisco SAN switch connected to the V/C modules and also to an EMC Clariion
The Cisco can see the V/C modules (e.g. it puts the ports into NPIV mode) but the switch can't see any of the blade HBAs. The switch can see two WWNs - but these bear no relation to the WWNs of the blade HBAs (one is vendor ID 10:00:00 the other is vendor ID 50:01:43)
The V/C is configured to connect the blades to the SAN, but no joy. I've tried with blades running both VMware and SLES 10, but neither works.
I don't know how to troubleshoot this thing (I'm starting to get out of my depth with fibre channel here...) Can someone point me in the right direction ?
Thanks,
GTG
I have a Cisco SAN switch connected to the V/C modules and also to an EMC Clariion
The Cisco can see the V/C modules (e.g. it puts the ports into NPIV mode) but the switch can't see any of the blade HBAs. The switch can see two WWNs - but these bear no relation to the WWNs of the blade HBAs (one is vendor ID 10:00:00 the other is vendor ID 50:01:43)
The V/C is configured to connect the blades to the SAN, but no joy. I've tried with blades running both VMware and SLES 10, but neither works.
I don't know how to troubleshoot this thing (I'm starting to get out of my depth with fibre channel here...) Can someone point me in the right direction ?
Thanks,
GTG
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-17-2007 04:22 PM
тАО12-17-2007 04:22 PM
Re: Fibre Channel Virtual Connect - blades not seeing SAN
Have you created a profile yet and then mapped it to the server.
And then defined which of the external VC-SAN ports the profile is seen out of?
And then defined which of the external VC-SAN ports the profile is seen out of?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-20-2007 07:23 AM
тАО12-20-2007 07:23 AM
Re: Fibre Channel Virtual Connect - blades not seeing SAN
Managed to fix this in the end...
The solution is simple, but very frustrating.
You have to switch EVEYRTHING off. Your fiber channel switches, the blades and the virtual connect modules. Switch 'em all off.
Then power up your F/C switches. Wait for them to boot up. Next, power-up the VirtualConnect modules, and wait for them to sign onto the F/C switches (this may take a while). Finally, you can switch on your blades and everything will work..
The solution is simple, but very frustrating.
You have to switch EVEYRTHING off. Your fiber channel switches, the blades and the virtual connect modules. Switch 'em all off.
Then power up your F/C switches. Wait for them to boot up. Next, power-up the VirtualConnect modules, and wait for them to sign onto the F/C switches (this may take a while). Finally, you can switch on your blades and everything will work..
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