[mike_antees]

Hi Folks,

I've been asked to review how NIM is being used in our company's environment. Basically we have a p590 at our HO site running multiple AIX 5.3 LPARS and a p570 at our DR site also running multiple AIX 5.3 LPARS. We have 7-10 LPARS at each site.

When NIM was first implemented a HO LPAR was dedicated to being the master to several HO NIM clients and likewise at our DR site also had its own master to serveral DR NIM clients. The are effectively separate entities.

I am concerned that if we could not start either master then all clients at each site would require on-site people to administer updates to the clients. We also have to travel to our DR siter to update the DR NIM master before sending the updates through to its clients.

I'm interested in improving this situation. If our our NIM DR master could be called upon to update the NIM HO master and all HO/DR clients and likewise our NIM HO master could be called upon to update the NIM DR master and HO/DR clients, our world would be a better place.

I'm not sure if a alternate master will facilitate this or setting up our HO and DR masters as clients to each other. We have only a 1 Gb comms link between the 2 sites and it is also a factor in the mix.

Any ideas on the best high level design? As I see it I have 3 options:

1. Leave it as it is and put up with the travelling.
2. Make our DR NIM LPAR an alternate master where there are slightly fewer clients.
3. Leaving each NIM Master in place and making them a client of each other.

Thanking you in advance
Mike

[steevojb]

Hi,

I would look at alternate master configuration

pSeries and AIX Information Center

Keep both NIM servers identical with client definitions for both sites on each server

HTH

Steve

[dthacker]

Mike,
I'm following along, because I'm in a similar position. I'm not familiar with the term HO (except in a model railroad context). What is that?

Dave

[steevojb]

Head Office

HTH

Steve

[mike_antees]

Thanks again Steve