- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: Changing disk numbers in MS 2008 R2 Fail over ...
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
тАО02-02-2012 03:24 AM
тАО02-02-2012 03:24 AM
Changing disk numbers in MS 2008 R2 Fail over cluster
What circumstances can trigger the disk numbering in MS W2008 R2 to be changed? I have a 2 node MS W2008 R2 fail over cluster and found that the disk numbers between the 2 nodes have changed and is now no longer in sync. I am using pass tru disks for VMs and this can in case of a failover cause the wrong disks to be exposed to the VM.
We use iSCSI initiator and I have found that MS W2008 R2 screws up the favorite target list, possibly when it can not access the favorite target during start up. Issues might be IPv6 and IPv4 enabled on the SAN NIC (not in our case) or when network configuration has been updated/changed (our case added 2 NICs).
Way to fix the disk numbering?
Can the disk numbering be made pesistent? That under no circumstance it can change?
TIA,
Fred
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2012 07:38 AM
тАО02-02-2012 07:38 AM
Re: Changing disk numbers in MS 2008 R2 Fail over cluster
After reading other posts on the internet the changing disk numbers seems to be default behavior in which case I can't believe windows would use the disk number to pass on as a disk identifier in case of a fail over or liveMigration. Would MS be so .....?
It must be a unique iscsi identifier used in which case the database holding the disk no, iscsi id has become unstable. Are there tools for debugging this?
Fred
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-02-2012 08:55 AM
тАО02-02-2012 08:55 AM
Re: Changing disk numbers in MS 2008 R2 Fail over cluster
"In Windows Server 2008 failover clusters, the disk signature and the LUN ID are both used when identifying a cluster disk resource. If either of these has changed, the cluster configuration is updated. This translates into a reduction in the errors that are simply due to an attribute change on a physical disk resource."
So MS is not using the disk no to identify the resource. Are there tools to troubleshoout this? Comparing GUID and LUN ID between server nodes? Checking these against VM disk settings.
What can make a LiveMigration associate the wrong disk based on GUID/signature as this should never have happened.
Fred