Announcement

Collapse
No announcement yet.
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
  • #1

    DHCP *ON* Shoreware director?

    My partner/installer is telling me that installing a DHCP server *ON* the Shoreware Director server is unsupported and unwise. The reason I was given is that ST recommends nothing be installed on the Shoreware Director server for any reason ever. That's understandable, but DHCP is so very low-resource and rarely used that it seems a bit of overkill to restrict it away from the Director server. Is there any other worry on this point?

    Also, should the Shoreware Director be added into the main network's Active Directory domain?

    Thanks for any help you can provide in advance.
    Tags: None
  • #2
    Most of our clients have joined all their ShoreTel servers to their domain. DHCP like most things is not supported on a ShoreTel server. In reality we see people operating outside of the scope of supported configurations. DHCP would probably be OK, but it might depend on the scale. If you have a lot of phones (and other devices) looking for IP addresses at the same time that a lot of phones are looking for the FTP server such as when the power to your PoE switches comes back on....

    Comment

    • #3
      I normally add the server to the domain. It makes management easier.

      Yes, the Shoretel server "SHOULD" only have Shoretel Services running on it. :hammer:

      That's not to say that is always true. I have a customer that is running his building access control system and 2 websites on his ST server, and he has never seen an issue (beefy server). He only has 50 phones though.

      In many "smaller" installations, those that may not have a proper network, or rely on a cheap router to perform DHCP, I have been known to add DHCP on the ST Server. But once again, these are under 30 networks.

      Charles

      Comment

      • #4
        DHCP on server

        We have our DHCP on the shoretel server and have had no issues.

        DHCP servier is such a low demand service that I believe having a background wallpaper on the server would take more resources.

        Our VOIP network is physically seperate than our DATA lan, so the *only* server on the voip network is the shoretel server. We allow limited interaction between the two networks from the data to the VOIP for call control with the PCM only (using ACL's), nothing back the other way.

        Anyone, long story short, I can not imagine a situation where that .05 percent CPU usage would cause you a problem (if you are talking about a few hundred phones or less).

        Comment

        • #5
          I will agree with Charles, in most situations ShoreTel ignores this trivial aspect. It might be easier for you to use the server as a DHCP server "SHORETEL IP PHONES ONLY"

          It is not uncommon for this to be done at all and really isn't that much in overhead on todays Server platforms. Take for instance the SBE from ShoreTel it is sefl contained and runs DHCP

          Comment

          • #6
            Thanks to all of your for your input. We're looking at 160 phones initially.

            Originally posted by eazeaz View Post
            Our VOIP network is physically seperate than our DATA lan, so the *only* server on the voip network is the shoretel server. We allow limited interaction between the two networks from the data to the VOIP for call control with the PCM only (using ACL's), nothing back the other way.
            This is the situation we're thinking of doing, and thus I'd have to put another server on that network JUST to do DHCP. $700 for another Windows Server license is overkill in that situation.

            How many phones are you using?

            Also, our partner is saying that an additional router between these two networks can introduce additional latency, which could impact any softphones on the main data network or on the Internet. How much of a concern is this? I have no idea how much we'll use softphones if at all, but I don't wnat to do anything that will limit us in the future.

            Thanks for the help, all.

            Comment

            • #7
              Networks

              We have almost 100 phones. I would think that 1000 phones would be no issue.

              An additional router between your two networks (voip and data) will add about .5ms latency. You will have no issues caused by the additional router.

              If you do VLANS with layer 3 switches you are using the layer 3 switches as a router between the vlans.... same thing.

              We have been very happy with the separation of the two networks. Most QOS issues go out the window, no data/voip contention. We can work on one network without affecting the other. We don't have to worry about expensive POE gigabit switches (we are gig to the desktop), buying gig phones, etc.

              it has been a wonderful deal.

              The abillity to have Access lists and control over what data goes between the two networks, and not having to worry about the complexities of vlans, qos, etc are a big plus.

              We found that we saved a bunch of money by running an additional drop to each desk instead of buying expensive POE gigabit switches.

              Comment

              • #8
                Sounds good, Eaz. You've made my life much easier with your answers. I think I'm going to go back to my original plan (outlined above). Not sure about the DHCP thing yet, but I have confidence that DHCP on the Director will not cause issues.

                Confidence based on zero experience, but only on you all's statements here. Thanks again.

                Comment

                Previous template Next
                Working...
                X