Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Multiple routes for IP resource in VCS

Created: 17 Sep 2012 • Updated: 19 Jul 2013 | 3 comments
dveeden's picture
1 Agree
0 Disagree
+1 1 Vote
Login to vote
Status: Alternative Solution

The IP resource supports one route via the IPRouteOptions attribute. In a number of cases this is not enough.

A workaround is to add an Application resource and then use "ip route add ..." as StartProgram and "ip route del..." as StopProgram. As MonitorProgram a script is used which will check if the route exists or not. The monitor script then will use exit code 100 or 110.

The workaround will create a more complex and error prone resource dependencies.

A possible solution is:

Add a IPRouteOptionsFile attribute which can hold a filename. In the file there can be multiple routes, each on one line. The file should support comments to make it easier for administrators to distinguish between routes.

Comments 3 CommentsJump to latest comment

Paresh Bafna's picture

Could you please let us know your exact use case of adding/deleting multiple routes when IP resource is brought online/offline?

Also as a workaround, there are various triggers like postonline, postoffline and resstatechagne which can be used to invoke user script to add/delete multiple routes on resource online/offline.

Please refer to VCS Admin Guide of appropriate version for more details.

Hope this helps!

Thanks and Regards,
Paresh Bafna

Thanks and Regards,
Paresh Bafna

0
Login to vote
Piwik's picture

Regular expression or matches in Search Rules do not appear to work with IP addresses, otherwise this would be an easy fix.
What's required here is when selecting IPaddress in Search Rules that you can also use regular expression or ranges to accommodate this.
Transforms do not work either.
So I guess the answer is 'this isn't currently supported by VCS'

0
Login to vote
dveeden's picture

The exact use case:

We use TIBCO in a VCS cluster. We need to reach systems in two subnets. By default the source IP will be the IP of the node, not the shared cluster IP. For both subnets we need to set a route to make sure that the source IP will be the cluster IP address.

We do have a work around which works OK, but a more clean long term solution would be appreciated.

0
Login to vote