[kvellimalai]

Hi All,
We have 12 LPARS defined on a P570 and NIM was configured. due to some administrative tasks we have moved all these LPARS to different subnet. and communication is working fine. I had an issue with NIM backup and resouce allocation and not working fine. when i did a niquerry i found the nim is configured with old IP address. I removed all the machines from the nim definition, unconfigured the mater net and removed /etc/niminfo file from the master server and nim clients. After this I configured the NIM with new values and the defined the client machines.
did a niminit from client machine to get all correct information and /etc/nimfo file has the current values.
When i did a nimquerry on the master server for a client machine, i am still getting the old gateway address and not the new one.

===================
NIMSH Client Values
===================
hostname = sydb2srs1b
IP address = 172.20.148.241
subnetmask = 255.255.255.0
gateway = 172.20.136.1
interface = en0

====================
NIMSH Client Options
====================
SSL Enabled = no
Push Denied = no
Restricted Shell = no

I am not sure where I did the mistake.
Please help me to fix it.

Regards
Velli

[steevojb]

Hi there,

nimquery will retrieve the gateway from the master. Have you changed the gateway properly on your master ?

lsattr -El inet0
netstat -rn

HTH

Steve

[kvellimalai]

Hi Steve,
Thanks for the response. Yes I have changed the route information in the master.
See the results below as you requested.

(root@sydb2srs1a) /var/nim/local_scripts =>lsattr -El en2
alias4 IPv4 Alias including Subnet Mask True
alias6 IPv6 Alias including Prefix Length True
arp on Address Resolution Protocol (ARP) True
authority Authorized Users True
broadcast Broadcast Address True
mtu 1500 Maximum IP Packet Size for This Device True
netaddr 172.20.148.240 Internet Address True
netaddr6 IPv6 Internet Address True
netmask 255.255.255.0 Subnet Mask True
prefixlen Prefix Length for IPv6 Internet Address True
remmtu 576 Maximum IP Packet Size for REMOTE Networks True
rfc1323 Enable/Disable TCP RFC 1323 Window Scaling True
security none Security Level True
state up Current Interface Status True
tcp_mssdflt Set TCP Maximum Segment Size True
tcp_nodelay Enable/Disable TCP_NODELAY Option True
tcp_recvspace Set Socket Buffer Space for Receiving True
tcp_sendspace Set Socket Buffer Space for Sending True
(root@sydb2srs1a) /var/nim/local_scripts =>lsattr -El inet0
authm 65536 Authentication Methods True
bootup_option no Use BSD-style Network Configuration True
gateway Gateway True
hostname sydb2srs1a Host Name True
rout6 IPv6 Route True
route net,-hopcount,0,,0,172.20.148.1 Route True
(root@sydb2srs1a) /var/nim/local_scripts =>netstat -rn
Routing tables
Destination Gateway Flags Refs Use If Exp Groups

Route Tree for Protocol Family 2 (Internet):
default 172.20.148.1 UG 8 62397 en2 - -
127/8 127.0.0.1 U 65 134971 lo0 - -
172.20.148.0 172.20.148.240 UHSb 0 0 en2 - - =>
172.20.148/24 172.20.148.240 U 2 27575 en2 - -
172.20.148.240 127.0.0.1 UGHS 21 161679 lo0 - -
172.20.148.255 172.20.148.240 UHSb 0 4 en2 - -

Route Tree for Protocol Family 24 (Internet v6):
::1 ::1 UH 0 0 lo0 - -

[kvellimalai]

After spending some attempts i found the problem is in the odm and odm is having the route definition for inet0 with old gateway. I removed fit from the ODM level. But still i was unable to change the attribute on the master server. I unconfigured nim totally and tried to configure again. But i am getting an odm error saying nimerror no =5190.

anyone encountered this. If yes, can you please help me to come out of this?

Regards
Velli

[john.samons]

I've found that NIM seems to visit the pub alot... I've seen this on a customers site before.

First had to fix the odm and get that entry out of the inet0 device. Thereafter NIM was still a bit confused. Unconfigured and reconfigured just seemed to make it drive in circles...

Uninstall the file sets, and reinstall solved that problem.