Overview of affect at changed.
IP Address only is changed:
- For Linux/UNIX PIM/PAMSC Endpoint:
TERMINAL class may be affected, if the TERMINAL is defined using the IP address.
The TERMINAL record should be updted to reflect the new IP address.
LADB should rebuild after changed IP.
Restart PIM/PAMSC daemons.
Make sure that any of the name resolution software/application like DNS/DHCP etc are appropriately updated as well.
If the TERMINAL class record is defined using the hostname, no changes to the TERMINAL record is required.
LADB should rebuild after changed IP.
Restart PIM/PAMSC daemons.
Make sure that any of the name resolution software/application like DNS/DHCP etc are appropriately updated as well.
- For Windows PIM/PAMSC Endpoint:
If TERMINAL class record is defined by hostname, a change in only the IP it does not affect the TERMINAL class record.
Make sure that any of the name resolution software/application like DNS/DHCP etc are appropriately updated as well.
--------
If hostname only is changed:
- For PIM/PAMSC Endpoint deployed on Linux/Unix/Windows OS:
TERMINAL class may be affected when it is defined by hostname.
New hostname's rule should be added in TERMINAL class records and authorizaion also needs to be provided to the users fror the new TERMINAL class record for the PIM/PAMSC endpoint host, this can be done before the actual change of the hostname.
Make sure that any of the name resolution software/application like DNS/DHCP etc are appropriately updated as well.
- Additional step for Linux/UNIX
LADB should rebuild after changed hostname.
Restart PIM/PAMSC serivce.
- No additional steps for Windows
No additional action.
--------
If both IP address and hostname are modified, steps mentioned above are to be performed in combination.