Wired Intelligent Edge

last person joined: 20 hours ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

Voice and Data vlan DHCP issues

This thread has been viewed 3 times
  • 1.  Voice and Data vlan DHCP issues

    Posted Apr 26, 2019 09:48 PM

    Hi

    I am trying to setup a for NEC VoIP phones that will feed the users PC 

    What happens when we test with laptops , No IP phones yet, is we get the DHCP from the Voice vlan, even when we untag the voice vlan

    Am I missing any commands?   or should I wait for phones to test further

     

    For the vlan configs I have below(Comments in )

    Vlan 100              (Range 10.1.100.0/24)

    name "Data"

    Untagged 1-24

    Tagged 48-52    (All trunk Ports)

    no ip address 

    ip helper-address 10.1.100.1  (Fortinet Router configured for DHCP)

    exit

    Vlan 110  (Range 10.1.110.0/24)

    Name "Voice"

    tagged 1-24 ,48-52

    no ip address

    ip helper-address 10.1.110.10   (NEC Voice server)

    Voice  (declared as Voice Vlan)

    Exit

    Thanks Much

     

    Craig

     



  • 2.  RE: Voice and Data vlan DHCP issues

    Posted Apr 27, 2019 03:04 AM
    It’s not needed to set a IP helper when the dhcp server is in the same segment. Also the ip helper address is useless because there is no ip interface at this switch.

    I suppose that the nec voice server is attached to the data vlan. Is the voice server also connected at this switch?


  • 3.  RE: Voice and Data vlan DHCP issues

    Posted Apr 27, 2019 11:25 AM

    Thanks,  I am sure the NEC team connected the voice server to a tagged voice, untagged data port  I can check   Also I will try adding an IP interface for the data vlan

    Craig



  • 4.  RE: Voice and Data vlan DHCP issues

    Posted Apr 27, 2019 12:04 PM
    Try to connect the server to an untagged voice port and remove the data vlan from the port. In most cases voice server are sending untagged traffic