| Ed Leatherman 2008-01-02, 7:11 pm |
| Hi Paul,
The infoblox systems we use are actually just running a linux kernel of some
sort underneath the cover.. supposedly you can even load PERL scripts and
stuff onto them as well to manipulate logs and so forth. I think what your
getting mainly at least with DHCP on infoblox and some of the others is the
clustering capability along with a graphical UI and the ability to offer
different views onto the system based on user / user class, as well as
support. I'm sure a straight up *nix box could do all that as well other
than the clustering which i'm not sure about. At least in my case we don't
have any staff really with up to date Unix training or background, so the
appliance type products like infoblox makes sense for us.
I can't think of any compelling reason to use infoblox over a straight-up
TFTP server for firmware updates. Its just handy for us since we already
have the nodes in strategic places for DHCP anyway. I dont think you would
be able to serve up IP phone configs from a generic TFTP server without some
scripting of your own to sync with callmanager however.
On Jan 2, 2008 4:47 PM, Paul Choi <asobihoudai@yahoo.com> wrote:
> I hope nobody takes this as a thread hijacking. I
> wanted to know if anybody uses a plain *nix server for
> their TFTP/DHCP needs as those kind of servers have
> been around for decades and used as such. Are there
> any drawbacks to just setting up a *nix boxen for
> serving DHCP/TFTP needs as opposed to third-party
> applications?
>
> Paul
>
>
>
> ________________________________________
________________________________________
____
> Never miss a thing. Make Yahoo your home page.
> http://www.yahoo.com/r/hs
>
--
Ed Leatherman
Senior Voice Engineer
West Virginia University
Telecommunications and Network Operations
|