A Forum reader recently asked:

“I’m installing a new BorderManager server. To avoid changing proxy setting on 450 machines, I’m moving the IP address to the new machine. How can I assign it to a new IP so I can transfer the rules?”

And here the response from Craig Johnson …


You need to change the private IP address on the old server, and add back the old one as a secondary. I do this a lot, as it makes it easier to replace the server, and it’s required if you want to cluster the server (cluster BorderManager).

I do it this way –

1. Change the private address in INETCFG,

2. Make sure the HOSTS and HOSTNAME files are also changed.

3. Use NRM to look at any other address assignments that might need to be changed.

4. In autoexec.bat, add back in the old address as a secondary.

5. In Monitor, Server Parameters, NCP and SLP options, include the new primary IP address. If you had the old one in there, you need to change it.

6. Reboot the server. You should probably reboot your PC as well.

If BMgr loads, it should be fine on the server end.

0 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 50 votes, average: 0.00 out of 5 (0 votes, average: 0.00 out of 5)
You need to be a registered member to rate this post.
Categories: Uncategorized

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.

Leave a Reply

No Comments
Dec 6, 2007
9:13 am
Active Directory Authentication Automation Cloud Computing Cloud Security Configuration Customizing Data Breach DirXML Drivers End User Management Identity Manager Importing-Exporting / ICE/ LDIF Intelligent Workload Management IT Security Knowledge Depot LDAP Monitoring Open Enterprise Server Passwords Reporting Secure Access Supported Troubleshooting Workflow