Callmanager 5.1 subscriber installation issue

Unanswered Question
Sep 1st, 2008

Hi,

Trying to add a second subscriber into a cluster, getting the error,

execution of script sd_hostsetup -add

failed with return-code 256.

the subscriber is located on a different site to the publisher but the routing and round trip delay is excellent.

any advice would be welcome.

Thanks

N

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Jaime Valencia Mon, 09/01/2008 - 09:41

are you installing the EXACT SAME version on SUB??

have you already added it to the CUCM config on PUB??

HTH

java

if this helps, please rate

norm.trees Tue, 09/02/2008 - 02:39

Hi,

the version was different, but reinstalled again with the same version that is on the publisher and the existing subscriber. The error message is returned, after installing and ejecting the DVD, the system reboots normally runs a few more scripts then fails,

the exact error message is,

The installation has encountered a unrecoverable internal error. For further assistance report the following information to your support provider.

Execution of script "/usr/local/bin/base_scripts/sd_hostsetup -add UKIPT01 172.16.1.1 UK.LOCAL >/common/log/install/capture.txt 2>&1" failed with return-code 256

The system will now halt.

The IP address, hostname and domain name in the above is that of the publisher.

The Server was added on the publisher under System - Server - Add New, using the hostname UKIPT04.

I am building the new subscriber on a remote site, the routing is working fine and the round trip time is excellent.

Any ideas ?

Thanks

N.

Jaime Valencia Tue, 09/02/2008 - 06:24

is there the right DNS resolution all thw way between pub and sub??

have you confirmed the server supports the version you're trying to install??

HTH

java

if this helps, please rate

norm.trees Thu, 09/04/2008 - 07:04

Hi, yes the DNS is ok, unable find any docs to see if the server was supported by the version that was supplied with it.

As it was a new server, the supplier is going to replace it, so hopefully it was a server fault or version/hardware conflict.

Thanks for you help & input!!!

Much appreciated!!!

Actions

This Discussion