well crumbs, as best a can tell, nether this phone system, fortiswitch model, or fortigate model will do the lldp response
On Tue, Apr 5, 2016 at 2:42 PM, Sovereen, David A < [email protected]> wrote: > Correct. > > Your switch will send out an LLDP packet that will advertise that VLAN 200 > is available on this port and is the Voice VLAN and the phones will then > boot up and operate on that VLAN. Cisco switches, by default, send out > LLDP packets every 30 seconds (I think) and some phones only watch for LLDP > packets for a shorter period. There is a command, I think “lldp timer 5” > that causes the Cisco switch to send LLDP packets out every 5 seconds, > which eliminates issues where the phone might not have “seen” the LLDP > packet and boots up on the Data VLAN instead of the Voice VLAN. > > All your other devices will ignore that, and just operate on the untagged > VLAN like normal. > > Dave > > On Apr 5, 2016, at 2:41 PM, That One Guy /sarcasm < > [email protected]> wrote: > > These are Fortigate phones with native support for that option. but I can > see the issue if other devices also have it enabled > The phones do not defaultly have CDP enabled, so that is not an option > LLDP is Enabled by default, however I have historically only looked at > LLDP ad a hand packet to look for if I need to identify a device in > wireshark > > LLDP, in this case im assuming would allow me to specify the VLAN for the > device type (voice=200) eliminating the issue of a printer or some other > device being placed into that VLAN if its got 132 enabled?? > > > > On Tue, Apr 5, 2016 at 1:03 PM, Sovereen, David A < > [email protected]> wrote: > >> DHCP option 132 support is sketchy and will vary a lot from manufacturer >> to manufacturer, and even model to model within a manufacturer. >> >> The more common approach to this is CDP and/or LLDP support, where a VLAN >> is announced as the Voice VLAN. Most (maybe 75% of handsets out there) >> will see the LLDP packet, and assuming VLAN 200 is marked as the Voice >> VLAN, will boot up and operate on VLAN 200, and pass through all other >> (untagged and tagged for other VLANs) traffic to the tethered Ethernet port. >> >> On Cisco switches, the command is switchport voice vlan 200 >> >> (200 being the VLAN in your example) >> >> If your phones won’t respond to CDP (Cisco proprietary) but will respond >> to LLDP (standard), you’ll need the command “lldp enable” on Cisco switches >> to enable LLDP support. >> >> Dave >> >> On Apr 5, 2016, at 1:51 PM, That One Guy /sarcasm < >> [email protected]> wrote: >> >> Im setting up a new VOIP system for a contract customer. >> >> We are putting the PBX and handsets on vlan 200 say. >> The phone supports option 132 natively, it seems to pull the initial >> address from the primary scope, apply the VLAN then pull from the secondary >> scope. >> >> These have a secondary gigabit port for tethering another network device, >> like a PC or printer, or whatever. >> >> My big question is how many devices are option 132 enabled? is this a >> standard thing or will most devices ignore it? >> >> I am looking to simplify the provisioning process as best I can while >> still providing the client flexibility to tether devices. >> >> This is a new build with 81 network drops, 20 of which are dedicated POE >> ports for the phones. If a phone needs replaced I would prefer no not have >> to log in directly to set the VLAN >> >> -- >> If you only see yourself as part of the team but you don't see your team >> as part of yourself you have already failed as part of the team. >> >> >> > > > -- > If you only see yourself as part of the team but you don't see your team > as part of yourself you have already failed as part of the team. > > > -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.
