[VOIPSEC] CCM 4.2 independant DHCP and TFTP servers
Erick Bergquist
erickbee at gmail.com
Fri Jun 9 23:12:35 CDT 2006
For DHCP, you can use any DHCP Server that you can specify option 150
with for TFTP server IP address. IMHO, it's a good idea to put this
off the CCM server to save on resources, etc.
TFTP is a bit trickier, as CCM TFTP process builds the config files,
etc that devices need. You need the service running on one server to
do this, and under TFTP service service parameters set it to build all
files and not cache them. The TFTPPath folder is a mapped/shared drive
by default also. So once TFTP is set up this way, you could run a TFTP
server on another system and point it to the TFTPPath folder share on
the CCM server or perhaps copy that folders/subfolder contents to
another server and use a syncing tool to keep the 2 in sync. This
defiantly would not be something supported by cisco, and probably not
tested. I haven't tried this but in theory it should work. The MOH
(IPVSM) files are also stored in the TFTPPath folder also so you want
to test this out and see what other features may be effected. The
TFTP service also has a service parameter for the path of the TFTP
files but I wouldn't suggest putting that offbox, as it could impact
CCM performance. You could have a dedicated CCM cluster node for TFTP
but it sounds like you are trying to avoid doing that.
On 6/9/06, TYBERGHIEN Eric F_T <eric.tyberghien at orange-ft.com> wrote:
>
> Hello everybody
>
> I'm looking for practical documentation or best practices guidelines in
> order to design opensource DCHP and TFTP servers for a large Windows Cisco
> CCM 4.2 architecture.
>
> I don't want to be too tied to Cisco proprietary rules (all TFTP and DHCP
> servers on CCM cluster's) for performance reasons and maximum opportinity
> of changing technology (another supplier, for example).
>
> Thanks for your experience returns
>
> Best Regards and nice WE
>
>
> Eric Tyberghien
>
> Senior Security Consultant
>
> Orange Business Systems
>
> SCE/GCS/Tech&PO/RSS (Réseaux Sécurité Solutions)
> Tel : 02 23 28 31 00
> Port : 06 82 81 51 85
> Fax : 02 23 28 45 81
> Email : eric.tyberghien at francetelecom.com
>
>
>
> *********************************
> Ce message et toutes les pieces jointes (ci-apres le "message") sont confidentiels et etablis a l'intention exclusive de
> ses destinataires.
> Toute utilisation ou diffusion non autorisee est interdite.
> Tout message electronique est susceptible d'alteration. Le Groupe France Telecom decline toute responsabilite au titre de
> ce message s'il a ete altere, deforme ou falsifie.
> Si vous n'etes pas destinataire de ce message, merci de le detruire immediatement et d'avertir l'expediteur.
> *********************************
> This message and any attachments (the "message") are confidential and intended solely for the addressees. Any unauthorised
> use or dissemination is prohibited.
> Messages are susceptible to alteration. France Telecom Group shall not be liable for the message if altered, changed or
> falsified.
> If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
> ********************************
> _______________________________________________
> Voipsec mailing list
> Voipsec at voipsa.org
> http://voipsa.org/mailman/listinfo/voipsec_voipsa.org
>
More information about the Voipsec
mailing list