Check connection (rsh or nimsh) between NIM server and LPAR
Article Number: 514 | Rating: 5/5 from 3 votes | Last Updated: Thu, Feb 21, 2019 8:11 PM
NIM server needs to be connected with LPARs, either using rsh or nimsh protocol. In case this communcation is lost, mksysb backups or other tasks from NIM to this lpar will fail. So, I have made this simple script to check this connectivity between NIM and LPAR.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
#!/usr/bin/ksh # Copyright (C) 2012 Israel Garcia iga3725 @ yahoo.com # # This program is free software: you can redistribute it and/or modify # it under the terms of the GNU General Public License as published by # the Free Software Foundation, either version 3 of the License, or # (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program # You need to add parameter $1 as the name of the lpar (machine resource) to the script: # # Check machine resource exist on NIM: lsnim -c machines| grep "$1" 1> /dev/null if [[ $? - eq 0 ]] ; then echo else echo "ERROR: $1 machine resource does not exists on NIM." && exit 1 fi # nim -o lslpp $1 | grep bos.rte.odm 1> /dev/null if [[ $? == 0 ]]; then echo "Communication NIM-LPAR $1 is OK!!" else echo ; echo "ERROR: There's no connection between NIM and LPAR $1. Check configuration." fi echo |
Just thanks if the post was helpful