cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - If community subscription notifications are filling up your inbox you can set up a daily digest and get all your notifications in a single email. X

CLX ETH Redundancy Option

Invalid_String
10-Marble

CLX ETH Redundancy Option

If my KepServerEx V6 instance has two separate network connections to a pair of EN4TR com cards in a CLX rack,  This is to give me redundant com paths to the critical systems.

 

Is there a way to configure them in a redundant\failover architecture within KepServerEx?

 

I know this can be done with an external router but I was hoping there was a native solution.

 

 

ACCEPTED SOLUTION

Accepted Solutions

@Invalid_String 

 

The link tag function would not work since there would be a secondary path. The two channels cannot be named the same and the Link Tag does have the functionality to recognize the secondary path.

 

Thanks,

*Chris 

View solution in original post

4 REPLIES 4

@Invalid_String 

 

The functionality you have described could possibly be done with Media Level Redundancy. Here is a link to the Kepware knowledge base article that covers the use of Media Level Redundancy:

 

Article - CS304183 - Media Level Redundancy feature with PTC Kepware Products

 

You can your MyKepware login credentials to access the article.

 

I also recommend opening a support ticket with the Kepware team to analyze your specific architecture. Here is a link to the login page where a ticket can be logged:

 

Log In | My Kepware

 

Thanks,

*Chris

@cmorehead 

Are linked tags supported with Media Level Redundancy?

I have a large number of linked tags between an OPC DA server and this CLX ETH instance.

IF a failover were to happen, would the linked tags still function?

 

Since mirror tags are created on the secondary device, I suppose it is possible that the linked tag read/write request referencing the primary tag would just use the secondary path.

@Invalid_String 

 

The link tag function would not work since there would be a secondary path. The two channels cannot be named the same and the Link Tag does have the functionality to recognize the secondary path.

 

Thanks,

*Chris 

That is disappointing, but I'm happy to know it up front so no time is wasted in testing.

I may just setup two linked tag groups and two individual channels with one CLX device in each.  Each linked tag group would reference a single CLX Eth instance.
The failover would be a manual operation to disable one linked tag group and enable the other, but at least i would have my redundant paths.\

 

Thanks for the info.

Announcements


Top Tags