- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- FC Path Recovery not working on Windows Servers
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
06-18-2014 04:21 AM
06-18-2014 04:21 AM
FC Path Recovery not working on Windows Servers
Hi,
i have following Blade System:
- c3000 BladeEnclosure (OA FW: 4.21)
- 2x VC Ethernet Modules (FW: 3.30)
- 2x VC 4GB/s FC Modules (FW: 1.42)
- 8x BL460c G1 with QLogic Dual Port 4GB FC HBA
On some of my Blade-Server is Windows Server 2008 R2 installed (incl. MPIO HP Drivers). Two servers in the same Enclosure have installed ESXi.
I recently updates my Brocade FC SAN Switches. This is because two of my four pathes to the EVA4400 LUN went down. Thats ok... BUT my Windows Servers did not recovered the two failed pathes - see my Screenshot. My ESXi Servers in the same Enclosure did?! I was a little confused.
So i tried to reconnect the failed pathes an found two workarounds:
1. Restart the whole Windows Server
2. Set the affected FC Port in my Virtual Connect Server Profile to "Unassigned" => Save => Connect the affected FC Port again to its Fabric like before.
So my question is:
Is this behavior normal? I dont think so. I thought the windows server should re-enable the failed pathes automaticly if restarted Switch is back online - like the ESXi do. I have seen other Windows Server on other customer Installations which reconnect their FC Pathes if they are back online again.
Any ideas or Tips? Are there any Settings i should check?
Thanks!
Best Regards
Marco