- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: EVA5000 to EVA8000 data replication problems
HPE EVA Storage
1752278
Members
4850
Online
108786
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
тАО08-06-2006 08:33 AM
тАО08-06-2006 08:33 AM
EVA5000 to EVA8000 data replication problems
We start replication from EVA5000 to EVA8000, after normalization and few days of normal operation TRU64 cluster practicaly hanged (only ping worked). In ES45 console wwidmgr also need very long time to return results and disk were not seen.
After 2 hours EVA5000 rebooted each controller and everything become normal. After few days at same event we simply powered off EVA8000 and after few seconds EVA5000 normalized. Vdisk that were not in DR Groups responds normaly all the time.
SAN is simple topology and both EVAs are on same switch. EVA5000 is crossed and EVA8000 is straight connected.
We also set Aptpolicy to 1, no effect.
fabric 1 with 2 4/32 FC SW (fw 5.0.3)+ 1 1/16 FC SW( fw 2.6.2)
fabric 2 with 2 4/32 FC SW (fw 5.0.3)+ 1 1/16 FC SW( fw 2.6.2)
EVA5000 3.028
EVA8000 5.110
CV 5.0.0.208
near time of event we can see in event log " Unknown Indicated Virtual Disk has transitioned to Stalled Too Long " and sometimes also "The Data Replication Path between this Site and the Alternate Site has closed, possibly due to a connection failure between the specified host port and the Alternate Site"
Any ideas?
Regards
Andrej
After 2 hours EVA5000 rebooted each controller and everything become normal. After few days at same event we simply powered off EVA8000 and after few seconds EVA5000 normalized. Vdisk that were not in DR Groups responds normaly all the time.
SAN is simple topology and both EVAs are on same switch. EVA5000 is crossed and EVA8000 is straight connected.
We also set Aptpolicy to 1, no effect.
fabric 1 with 2 4/32 FC SW (fw 5.0.3)+ 1 1/16 FC SW( fw 2.6.2)
fabric 2 with 2 4/32 FC SW (fw 5.0.3)+ 1 1/16 FC SW( fw 2.6.2)
EVA5000 3.028
EVA8000 5.110
CV 5.0.0.208
near time of event we can see in event log " Unknown Indicated Virtual Disk has transitioned to Stalled Too Long " and sometimes also "The Data Replication Path between this Site and the Alternate Site has closed, possibly due to a connection failure between the specified host port and the Alternate Site"
Any ideas?
Regards
Andrej
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2006 02:26 AM
тАО08-07-2006 02:26 AM
Re: EVA5000 to EVA8000 data replication problems
Some more info
It looks that this is only TRU64 Cluster and CA related, other nodes with replicated disks works normal.
If cluster nodes are booted and halted before came up completely, boot disks are not accessible in console until replication is disabled or after appr. 2 hours EVA5000 automaticaly reboots its controllers.
It looks that this is only TRU64 Cluster and CA related, other nodes with replicated disks works normal.
If cluster nodes are booted and halted before came up completely, boot disks are not accessible in console until replication is disabled or after appr. 2 hours EVA5000 automaticaly reboots its controllers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-21-2006 10:59 PM
тАО09-21-2006 10:59 PM
Re: EVA5000 to EVA8000 data replication problems
This was CA problem and only TRu64 had real problem with, all other hosts survived.
For CA I zoned together 1st 4 ports of EVA8k and 4 ports of EVA5k, other 4 ports of EVA8k are used for host conection. After that change there are no more problems or errors on EVAs.
For CA I zoned together 1st 4 ports of EVA8k and 4 ports of EVA5k, other 4 ports of EVA8k are used for host conection. After that change there are no more problems or errors on EVAs.
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