Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
NIM location
- Thread starter THOR01
- Start date
I don't see a huge issue. The nim server doesn't need to be on the same physical subnet as the server it is performing maintenance on. Obviously you'll have potential firewall issues that you may or may not have to work out.
I think the biggest potential issue would be network throughput (not necessarily latency). Do you have a good connection to your nim server? Assuming you'll be dumping mksysb images to it, you'll need to have a good amount of bandwidth or they'll take a long, long time. Same goes for patching and other maintenance tasks.
I think the biggest potential issue would be network throughput (not necessarily latency). Do you have a good connection to your nim server? Assuming you'll be dumping mksysb images to it, you'll need to have a good amount of bandwidth or they'll take a long, long time. Same goes for patching and other maintenance tasks.
I advice you to read this redbook and focus on best practices section:
IMHO adding to spamly comment, I think you can define a network on your remote NIM to optimise and direct packet movement in between!
Regards,
Khalid
IMHO adding to spamly comment, I think you can define a network on your remote NIM to optimise and direct packet movement in between!
Regards,
Khalid
- Thread starter
- #4
Sorry THOR01 but I have learned that by reading Redbooks, You will really gain more than just solving the problem you are having right now!- Thread starter
- #6
- Status
