Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • DHCP Issue build 13.23.69.10

    I have a new install that is having a DHCP issue. I can get the phone to work as long as I hard tag the phones. The DHCP scope says the phones are tagged Vlan 30 10.10.2.x, but they don't go there, they have the default address.
    The build is 13.23.6910.0 and we are using 212k phones.
    Server is 10.10.1.1, SG-90 @ 10.10.1.2 @ 10.10.1.4.

    The HP Switch in question is a 2650, @ 10.0.0.78

    All ODD Ports 1-47 are tagged in Voice VLAN ( 30)

    All EVEN Ports 2-48 are tagged in Default VLAN

    Ports 49 & 50 are untagged in default

    The Netgear switch has all ports untagged in default VLAN.

    The DHCP Server is: 10.0.0.4

    There are 4 DHCP Scopes, No SuperScope.

    10.0.0.0/16 – default data vlan

    10.10.0.0./16 – VOICE VLAN

    10.100.0.0/16 – PRIVATE WIRELESS VLAN

    10.101.0.0/16 – PUBLIC WIRELESS VLAN

    DCHP Relay is working for both the private and publics but we’re not using tagging.

    I have attached a chart of what works and what doesn't in case the format below is unreadable.

    ---- HP ----- NetGear
    VLAN ON VLANOFF --VLAN ON VLAN OFF
    PORT 50 DHCP ON FTP X X X X
    DialTone X X X X
    DHCP OFF FTP OK X OK X
    DialTone OK X OK X

    PORT 47 DHCP ON FTP OK OK
    DialTone OK OK
    DHCP OFF FTP OK OK
    DialTone OK OK

    PORT 48 DHCP ON FTP X X
    DialTone X X
    DHCP OFF FTP X X
    DialTone X X


    If we change the DCHP Scope option to VLAN tagging =0 and VLAN ID = 1 we’re able to get a phone
    to pick up a 10.0.4.x DHCP address w VLAN off and that phone can talk to a STATIC phone in the 10.10.2.x Range w VLAN=30

    I know I must be missing something. Any Ideas ?
    Last edited by rwensmann; 08-13-2014, 04:39 PM.

  • #2
    A few questions:

    On the port that the phone is plugged in to (say port 1), is it untagged DATA VLAN and tagged VOICE vlan?

    The port that your DHCP server is plugged into, is it untagged data VLAN and NO (in Procurve world) on the remaining vlans? It must be.

    Are you running your DHCP server on VMWare ESX (VMWare Infrastructure)?

    Comment


    • #3
      port1 is tagged Vlan 30 ( voice)

      DHCP server plugged into untagged port. not sure what you mean by "NO (in Procurve world) on the remaining vlans? " I am not familiar with it and will have to check with their network guy.


      not running on VMWare.

      Comment


      • #4
        DHCP Option 66

        From the ShoreTel docs:

        ShorePhone-IP110/115/210/212k/230/530/560/560g telephones are preconfigured to look for the ShoreTel serverís address to be specified as Vendor Specific DHCP option 156. If these options are not available, the ShoreTel IP phones will use option 66.

        We had to setup the DHCP server to provide option 66.

        Bill

        Comment


        • #5
          option 156 is set and the phones do pick up the vlan 30 tag as the scope designates.

          Comment


          • #6
            The phones should come up and get an IP address from the data vlan, then reboot and get one from the voice vlan (because the DHCP request is not tegged with the voice vlan id). Is this happening in your setup? Or is it getting a voice IP both times?

            You need to ensure that the option 156 is set on both the voice and data DHCP scopes and that it is the same on both.

            Comment


            • #7
              Several questions;

              Where is your DHCP scope located?
              What are the exact options of your DHCP scope+
              Is there a reason your have even ports set for no tagging and odd ports for tagging?
              Is there a reason your using different types of hardware (HP and Netgear)?

              ------------------------------------------------------------------------------------

              I use VLAN tagging in all of my offices. Voice DHCP scope on an Adtran router Data DHCP scope on the windows server, director is reached across MPLS cloud. Lately I have had to take the ftpserver setting out of Option 156 on the Data DHCP scope, aside from that I never have a problem.

              Comment


              • #8
                Chris nailed it

                Issue resolved. Chris nailed it with the call on the proserve!
                THANKS!!

                Comment


                • #9
                  I meant procurve! I guess I should proof before I post. Thanks

                  Comment


                  • #10
                    Has anyone had success using a Dell 6248P?
                    Last edited by neeper67; 07-09-2009, 05:51 AM.

                    Comment

                    Working...
                    X