Installation: The installation fails due to an invalid IP address

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(The installation fails due to an invalid IP address)
 
(One intermediate revision not shown)
Line 64: Line 64:
|-
|-
! '''Release'''  
! '''Release'''  
-
| Release 8.5(4), Release 9.0(1).
+
| Release 8.5(4), Release 9.0(1), Release 10.5(1).
|-
|-
! '''Associated CDETS #'''  
! '''Associated CDETS #'''  

Latest revision as of 07:21, 9 May 2014

The installation fails due to an invalid IP address

Problem Summary The installation fails because an invalid or incorrect IP address was entered when the node was added to the

cluster.

Error Message Installation failed due to invalid IP address.
Possible Cause An invalid or incorrect IP address was entered when the node was added to the cluster.
Recommended Action Use this procedue to correct an invalid secondary node IP address only while trying to add the node to

a MediaSense cluster but before it has been installed. Do not use this procedure after the server has been installed.

1) Enter 'set network cluster server' on the primary server to update the MediaSense cluster configuration with the correct IP address for the server which was incorrectly configured:

set network cluster server ip 10.10.10.93 10.10.10.136

where 10.10.10.93 is the invalid server address and 10.10.10.136 is the correct address to be set.

2) Enter 'show network cluster' to verify the interim cluster configuration:

Example response:

show network cluster

1 10.10.10.135 mcs-pri.cisco.com mcs-pri Primary authenticated using TCP since Mon Sep 12 12:53:16 2011

2 10.10.10.136 mcs-sec Secondary not authenticated or updated on server

3) Enter 'run sql select name,nodeid from ProcessNode' on the primary server to ensure that the IP address change is replicated to the secondary server database.

Example response:

run sql select name,nodeid from ProcessNode

name                         nodeid

EnterpriseWideData  1

mcs-pri                       2

mcs-sec                      3

4) Reboot the primary server to update the local name resolution files including the hosts, rhosts, sqlhosts, and services.

5) Enter 'show network cluster' to verify the interim cluster configuration again:

Example response:

show network cluster

1 10.10.10.135 mcs-pri.cisco.com mcs-pri Primary authenticated using TCP since Mon Sep 12 14:43:59 2011

2 10.10.10.136 mcs-sec.cisco.com mcs-sec Secondary authenticated

6) Go to the MediaSense Server Configuration list on the Administration page and confirm that the correct ip address is now showing for the secondary server.

Release Release 8.5(4), Release 9.0(1), Release 10.5(1).
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools