<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3429" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=095064018-27102008><FONT face="Lucida Sans"
color=#0000ff size=2>You can safely build it online. The services are not
activated during install so all you end up with is the entry in the
database. For Windows CCM you don't even end up with
System->CallManager entry until you manually activate the CCM
service.</FONT></SPAN></DIV>
<DIV> </DIV><!-- Converted from text/plain format -->
<P><FONT size=2>-Ryan </FONT></P>
<DIV> </DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> smithsonianwa@gmail.com
[mailto:smithsonianwa@gmail.com] <B>On Behalf Of </B>Tim Smith<BR><B>Sent:</B>
Monday, October 27, 2008 2:33 PM<BR><B>To:</B> Ryan Ratliff<BR><B>Cc:</B> James
Brown; cisco-voip@puck.nether.net<BR><B>Subject:</B> Re: [cisco-voip] CCM4.1.3 -
Add Secondary TFTP Server<BR></FONT><BR></DIV>
<DIV></DIV>Whats the actual recommended procedure for this one?<BR><BR>Wouldnt
you just build it online as a sub and then deactivate the CallManager services
that you dont need?<BR><BR>Cheers,<BR><BR>Tim.<BR><BR>
<DIV class=gmail_quote>On Mon, Oct 27, 2008 at 6:16 PM, Ryan Ratliff <SPAN
dir=ltr><<A
href="mailto:rratliff@cisco.com">rratliff@cisco.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">I'm
glad to hear you got it inserted manually into the database.
Frankly<BR>I'm amazed the install even proceeded if it couldn't reach
the publisher.<BR>
<DIV class=Ih2E3d><BR><BR>-Ryan<BR>-----Original Message-----<BR>From: <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>[mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>]
On Behalf Of James Brown<BR></DIV>
<DIV>
<DIV></DIV>
<DIV class=Wj3C7c>Sent: Monday, October 27, 2008 1:09 PM<BR>To: <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>Subject:
Re: [cisco-voip] CCM4.1.3 - Add Secondary TFTP Server<BR><BR>Just to close off
this thread, I got in touch with our vendor last week and<BR>was fortunate
enough to speak with an Ex-TAC engineer. The fix we<BR>implemented in the end
was:<BR><BR>1. Locate the installation log for the new server.<BR> -
Typically C:\Install\DBInstall\DBInstall00000000.txt<BR>2. Search this file
for two SQL queries on the "ProcessConfig" table.<BR>They will look
like:<BR> - INSERT INTO ProcessConfig (pkid, tkService, fkProcessNode,
paramName,<BR>tkParam, primaryData) VALUES
('{FD54F781-6D98-4EDA-8167-944514373EEC}',<BR>9,
'{735A18BD-974A-4896-9B9B-0F3F4DD3542F}', 'DBConnection', 3, 1)<BR> -
UPDATE ProcessConfig
SET<BR>paramValue='DSN=CiscoCallManager;SERVER=LOGISIPTTFT002;DATABASE=CCM0302;<BR>Trusted_Connection=yes'
WHERE paramName='DBConnection' and tkService=9
and<BR>fkProcessNode='{735A18BD-974A-4896-9B9B-0F3F4DD3542F}'<BR><BR>3. Bear
in mind that fkProcessNode value is a foreign key based on the pkid<BR>within
the ProcessNode table.<BR> - You therefore might need to change it to
match the pkid assigned for<BR>this new server.<BR> - The new pkid (and
therefore fkProcessNode) will become apparent when the<BR>new server has been
added via System->Server in CCMAdmin.<BR><BR>So it turns out that because
we built LOGISIPTTFT002 offline, the SQL<BR>INSERTS into the ProcessConfig
table on the publisher were not actually<BR>performed. As soon as we manually
executed the above statements, DBL Helper<BR>showed the new
server.<BR><BR>Apparently, after a reboot the HKLM\software\Cisco
Systems,<BR>Inc.\DBL\DBConnectionX registry strings are also updated
automatically.<BR><BR>Hope this helps someone in future.<BR><BR>All thes
best<BR><BR>James.<BR><BR>Ryan Ratliff wrote:<BR>> I'd strongly recommend
against messing around in the registry unless<BR>> you A) have a backup and
B) know what you're doing. If the database<BR>> connection string
wasn't correct the TFTP service wouldn't even start<BR>> on the
subscriber.<BR>><BR>> The correct registry entry for the db connections
is<BR>> HKLM\software\Cisco Systems, Inc.\DBL\DBConnectionX where X starts
at 0<BR>and goes up.<BR>> DBConnection0 should always be the
publisher.<BR>><BR>><BR>> -Ryan<BR>> -----Original
Message-----<BR>> From: <A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A><BR>>
[mailto:<A
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</A>]
On Behalf Of James Brown<BR>> Sent: Sunday, October 19, 2008 6:33
AM<BR>> To: <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
Subject: Re: [cisco-voip] CCM4.1.3 - Add Secondary TFTP Server<BR>><BR>>
Jason,<BR>><BR>> Thanks, that's a great help. I did activate the new
TFTP service<BR>> yesterday and as you described, the .conf.xml files
started appearing.<BR>> I'm guessing the TFTP and DBL Monitor service work
together to<BR>> generate these? I'll also remember to copy across the
phone loads<BR>manually.<BR>><BR>> One aspect which is really concerning
me though, is that the "Database<BR>> Connection Sring" field under the DBL
Monitor service parameters for<BR>> the new TFTP server is blank! That
field is also locked, so I can't<BR>> enter something
manually.<BR>><BR>> I did a "SELECT * FROM ProcessConfig WHERE ParamName
LIKE 'DBConection';"<BR>> and noticed that every server appart from this
new TFTP has an entry.<BR>> Also, when I run DBLHelper on the publisher, I
see every server except<BR>> this new one.<BR>><BR>> However, MSSQL
replication looks to be working within Enterprise<BR>> Manager. I also
tried manually adding a new registry key under<BR>>
"HKLM\Software\Cisco...\DBL\DBConnectionX", then deleted and readded<BR>>
the new TFTP to the cluster. No joy.<BR>><BR>> Perhaps this will get
resolved as part of the cluster reboot, but I'm<BR>> not hopeful. Does
anyone have any suggestions please?<BR>><BR>> Regards<BR>><BR>>
James.<BR>><BR>> Jason Burns wrote:<BR>>>
James,<BR>>><BR>>> 2. All of the device configuration files
like<BR>>> SEPXXXXXXXXXXXX.conf.xml are generated in memory when the
TFTP<BR>>> service starts. The TFTP service reads the phone
configuration from<BR>>> the database and by default never writes this
file out to disk. It's<BR>>> faster this way. You can change this
behavior in the TFTP Service<BR>Parameter page.<BR>>><BR>>> To get
things like new phone loads onto the TFTP server you would<BR>>> have to
run through the phone load installer on the new TFTP server<BR>>> or
extract the zip files into the TFTP directory.<BR>>><BR>>> 3.
Whenever you add a new server, a cluster reboot is necessary to<BR>>>
make sure all the other servers in the cluster know it is there.
This<BR>>> is so change notification will work properly. This will be
required<BR>>> even for a TFTP server because it will have to get
change<BR>>> notification to update the in memory config files when you
do<BR>>> something like change a CallManager group
around.<BR>>><BR>>> -Jason<BR>>><BR>>> On Fri, Oct 17,
2008 at 12:07 PM, James Brown<BR>>> <<A
href="mailto:james.m.h.brown@googlemail.com">james.m.h.brown@googlemail.com</A><BR>>>
<mailto:<A
href="mailto:james.m.h.brown@googlemail.com">james.m.h.brown@googlemail.com</A>>><BR>>>
wrote:<BR>>><BR>>> James Brown
wrote:<BR>>><BR>>>
All,<BR>>><BR>>>
[...]<BR>>><BR>>><BR>>> 1. How
do I get the new TFTP server recognised in the<BR>>>
servicability page on the publisher? My guess is that I'd
need<BR>>> to momentarily start the Call
Manager service on the new TFTP to<BR>>>
allow the heartbeat to begin. I can't see any way of manually<BR>>>
programming servers into the servicability
page.<BR>>><BR>>> 2. When I have all
the services configured correctly on this new<BR>>>
TFTP server, how should I begin getting the publisher to
sync<BR>>> the device config files out to
the new repository? Should this<BR>>> be
done by a manual copy/paste, or does the publisher<BR>>>
automatically start writing the files when it recognises a
new<BR>>> TFTP service is
started?<BR>>><BR>>> 3. This is a new
server in the cluster, with a copy of the CCM<BR>>>
database, but it's not actually going to have process callls.
Is<BR>>> a cluster reboot therefore
necessary?<BR>>><BR>>>
[...]<BR>>><BR>>><BR>>> I think I can answer
question 1 now. On CCM 4.x, the server can be<BR>>>
defined under System->Servers within CCMAdmin. Once it's added
on<BR>>> this screen, it should also appear within
Serviceability. No need to<BR>>> activate the CCM Service
on a TFTP Server.<BR>>><BR>>> I'm still unsure about
questions 2 and 3 though.<BR>>><BR>>><BR>>>
_______________________________________________<BR>>>
cisco-voip mailing list<BR>>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>
<mailto:<A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A>><BR>>>
<A href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>>><BR>>><BR>>><BR>>>
---------------------------------------------------------------------<BR>>>
-<BR>>> --<BR>>><BR>>>
_______________________________________________<BR>>> cisco-voip mailing
list<BR>>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>>
<A href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR>><BR>>
_______________________________________________<BR>> cisco-voip mailing
list<BR>> <A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR>>
<A href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target=_blank>https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>