- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Excessive data exchange retry rate
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-13-2008 07:32 AM
тАО02-13-2008 07:32 AM
Excessive data exchange retry rate
Problem Found:
CUST: CA warning: IDCEVA8100: Excessive data exchange retry rate on the inter site link.
Full Description:
Excessive data exchange retry rate on the inter site link is preventing acceptable replication throughput: Reducing data exchange resources. The UUID of the remote DR group and the UUID of the Peer storage system is stored in the FRU section. A summary of events have been consolidated in the evidence section.
Full Corrective Action Statement:
Check fabric switch settings and inter site link quality between the Data Replication Source Site controllers and the Data Replication Destination Site controllers.
Anyone have any ideas where to start looking to isolate the problem?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-13-2008 07:55 AM
тАО02-13-2008 07:55 AM
Re: Excessive data exchange retry rate
Then check the long-distance link, you'll need to contact the company providing it and the IP routers if it's a FC over IP link.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-22-2010 11:04 PM
тАО12-22-2010 11:04 PM
Re: Excessive data exchange retry rate
Moreover we have have 2EVA4000 and no such issues on these systems, they are replicating over the same ISL link and I'm sure that link (direct fc cable) is ok
What could be a problem?
Thannk you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-28-2010 01:22 AM
тАО12-28-2010 01:22 AM
Re: Excessive data exchange retry rate
The HP FC replication protocol is the one being used util now. It needs port-based routing and in-order delivery set on the SAN switches:
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c00590193
HP SCSI-Compliant replication protocol is the new one included on XCS 09534000 and does not need that.
Probably you have created the replication between the EVAs 4400 without looking at this.
Check the Continous Access Implementation Guide.
http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02491009/c02491009.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 12:32 AM
тАО12-29-2010 12:32 AM
Re: Excessive data exchange retry rate
the OP had this setup:
"12 Mb point-to-point circuit"
Is that enough??
As far as I understood it it works like this:
When an EVA has a DR-link and it needs to send something over it, it uses the whole link.
What if you have two EVAs on the same link?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-29-2010 08:21 AM
тАО12-29-2010 08:21 AM
Re: Excessive data exchange retry rate
The size of the DR link depends on how much data you want to replicate, it should be enough to transmit the average amount of data. That depends on the amount of data written to the vdisks being replicated. No easy way to calculate, you have to monitorize the written bytes to the vdisk.
The data is copied to the other EVA in 16 KB chunks, as many as will fit on the link. If you have two replications over the same link, they will share the bandwith, of course, like two apps on your computer downloading from the Internet connection.