Novell BorderManager provides Remote Access Solution through IPSec and IKE technologies. Administrators can define the networks to allow or deny access for specific users using iManager framework.
In BM 3.8 and BM 3.8 SP1 a traffic rule can contain multiple Destination Networks. But with later support packs a traffic rule can hold only one Destination network. The iManager framework restricts the administrator from adding more than one Destination network to a traffic rule. The Destination network can be either IP Address Range or a Network. So the Migration from BM 3.8 or BM 3.8 SP1 to Later Versions will have problems with Client-To-Site functionality. In the sense though the traffic rules are pushed to the client the networks cannot be accessed because of the technical constraint.
This tool will split the single rule with multiple networks into individual rules each containing a single network.
Note: Make sure there is no space after the commas
The rule with multiple networks will be split and added as single rules with corresponding networks.
Disclaimer: As with everything else at NetIQ Cool Solutions, this content is definitely not supported by NetIQ, so Customer Support will not be able to help you if it has any adverse effect on your environment. It just worked for at least one person, and perhaps it will be useful for you too. Be sure to test in a non-production environment.