Yup, that was a typo.
Quote:
Well, first off, the network IDs have to be unique, i. e. "subnet_1", "subnet_2", etc.. I suppose that was only a typo on your part.
Thanks. I thought it is necessary.
Quote:
To answer your question: yes, you will have to create separate NIM-networks for this. No, you won't have to configure 3 IP-aliases for your master.
Is this something that I need to check with our network team? We currently have 4 different subnets in our AIX lpars and they can talk to each other normally.
Quote:
The reason for this is: NIM operates using NFS (for "normal" package installations), bootp (for mksysb-installs) and tftp. All these protocols have to be - obviously - allowed by all the firewalls you might have in between your NIM-server and the prospective clients
Thanks for your help Bakunin.
P.S. Just joined the forums again after years of rest. I'm still trying to get the hang of using it properly.
- kaelu
---------- Post updated at 10:55 AM ---------- Previous update was at 10:52 AM ----------
Quote:
Originally Posted by
ibmtech
Just to add to bakunin's comments
When you are in sms menu for client (IPL where you configure the IP, Master IP subnet and gateway), say for IP 10.30.1.21 you will use the gateway of that client ex:10.30.1.1 and NOT the NIM gateway ex:10.20.1.1. Same goes with 10.40.1.X subnet.
Thanks ibmtech. Will remember this, I think I had issue regarding this when I'm trying to restore our VIO server via NIM.