1 Reply Latest reply on Nov 2, 2013 7:37 PM by jayh

    Netvanta 7100 Windows domain DHCP problems?

    outrider New Member

      I am relatively new to Phone systems, I was hired at a company that put me in charge of Networking. We just moved and are in the process of migrating our servers. Just before the move we from a 100.xxx.xxx.xxx schema to a 10.xxx.xxx.xxx schema. We have a Netvanta 7100 with adtran and polycom phones, and I am having huge problems configuring this thing correctly. We have 2 servers as DHCP hosts using options 66 and 157. I thought I had everything working correctly 2 days ago then when I went in today I couldn't get phones that were rebooted to register. I am seeing a lot of bad addresses in dhcp. Which makes me think there is a conflict somewhere. we are running most of the phones(about 50) from the netvanta 7100 ports to switches, then POEs, then the phones.

       

       

      Old server

       

      PDC- server 2003

       

      New servers

      2 x server 2012

      1 running a virtual file server and will be running virtual exchange

       

       

      Any suggestions?

        • Re: Netvanta 7100 Windows domain DHCP problems?
          jayh Hall_of_Fame

          We have seen several situations where Windows DHCP servers don't function properly in a multi-VLAN environment.  The failure mode most common to us is as follows:

           

          Data VLAN served by Windows DHCP server.  Phones in separate voice VLAN with a different DHCP server, typically the Adtran IAD.  Phones act in trunk mode, passing data VLAN to a PC plugged in to the pass-through port on the phone.

           

          PROBLEM:  If the Windows server on the data VLAN is connected to a switch port that has the voice VLAN available, it will hand out data VLAN addresses to the phones, even if the voice VLAN isn't programmed on the Windows DHCP server at all.  It will "jump" VLANs.  The phones then fail to register or communicate with anything on the voice VLAN because they're on the wrong subnet.

           

          The only fix is to connect Windows DHCP servers only to switch ports that are manually configured as access ports on the data VLAN only.  Don't try multiple scopes on the same Windows server for devices on other VLANs. 

           

          I recommend ensuring that your Windows DHCP servers are on switch ports set to access mode serving only the VLAN where the Windows DHCP clients reside.  Use the 7100 as the DHCP server for the voice VLAN.