- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Re: VC FC Errors and ESX 3.5 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
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
тАО12-28-2009 08:36 AM
тАО12-28-2009 08:36 AM
VC FC Errors and ESX 3.5 Servers
Last week my SAN admin and I were working on reconfiguring some disk in our environment. When the disk work was done, I looked for the LUN on the ESX hosts and noticed that nearly all 8 of my ESX hosts in 2 c7000's are having path issues.
My SAN admin says that there is nothing wrong with the SAN and he can see every WWN.
When I look at the VMware side, I see dead paths on some links, or no paths at all (yet VM's are still running on these ESX hosts).
When I look at the VC logs, I see a lot of strange errors about the FC state being degraded or "uplink ports have different SAN fabric WWNs." However there isn't much information to go on with these warnings.
Before I open a case with HP and/or VMware, I was hoping someone out there could shed some light on these errors in the attached log.
Here is the firmware revision list.
OA - 2.41
iLO - 1.77 (all 4 servers in chassis)
VC Ethernet - 2.10
VC Fiber - 1.32
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2009 11:38 AM
тАО12-28-2009 11:38 AM
Re: VC FC Errors and ESX 3.5 Servers
What happened 2009-10-11T22:30:23-05:00 ?
Does Your VCM show all OK ?
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2009 11:41 AM
тАО12-28-2009 11:41 AM
Re: VC FC Errors and ESX 3.5 Servers
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2009 11:46 AM
тАО12-28-2009 11:46 AM
Re: VC FC Errors and ESX 3.5 Servers
Both SAN fabrics show "Degraded" but all ports are green and have an "OK" status.
Everything else looks fine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2009 11:47 AM
тАО12-28-2009 11:47 AM
Re: VC FC Errors and ESX 3.5 Servers
Can you explain a little more about the uplinks not going to the same SAN? Would that be a FC switch configuration?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2009 11:53 AM
тАО12-28-2009 11:53 AM
Re: VC FC Errors and ESX 3.5 Servers
If You have two FC modules, You can't connect both to same fabric
You can find me from Twitter @JKytsi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2009 05:03 AM
тАО12-29-2009 05:03 AM
Re: VC FC Errors and ESX 3.5 Servers
for example if you create a single VC SAN, SAN_A for example, and assign all 4 uplink ports to it, then all 4 fibre cables MUST connect to the same external SAN (Switch)/Fabric. You cannot in this case connect ports 1 & 2 to Fabric_A and 3 & 4 to Fabric_B.
If you want to do that you should create 2 VC SANs, SAN_A1 (say) and assign ports 1 & 2 to this SAN, and a second VC SAN, SAN_A2 and assign ports 3 & 4 to it. You can now connect uplinks (ports) 1 & 2 to Fabric_A, and uplinks 3 & 4 to Fabric_B.
If you have a second VC FC module in the adjacent bay, then you can do the same there, by creating VC SANs, SAN_B1 and SAN_B2.
It IS legal to connect (for example) uplinks from both modules to the same external SAN switch, however they must be assigned in VC to different VC SANs.
Remember also, that these new SAN names must be propagated back into your Profiles to ensure that your VM's can continue to talk to their storage.
Just in case we are assuming too much, confirm that your SAN admin is seeing the VC assigned WWID's and not the Physical WWIDs.
Hope this helps.
Dave.