Boris,
That’s good information, I’m guessing CDP or LLDP is at work in identifying the
phone and it’s connected computer.
Sorry I can’t direct you where to look for an explanation on why the phone’s
MAC is getting registered instead of the PC.
What mechanism are you using to control VLAN switching, I’m guessing not
port-security because it uses defined MAC addresses in the interface commands
(port-security is the only thing I’ve ever tested.)
Steve
CSM
> On Mar 3, 2015, at 2:58 PM, Boris Epstein <[email protected]> wrote:
>
> Steve,
>
> Thank you very much!
>
> Actually, the VoIP phone somehow automatically attached itself to the voice
> VLAN whereas the PC fell into the registration VLAN at first - also
> automatically - and then migrated to the production VLAN when I registered it
> - all without a hitch. The only problem was, the MAC address that PF detected
> - and the one I had to operate on - was not that of the PC I meant to
> register but that of the Polycom phone. And the weird thing was that in spite
> of that I still managed to successfully register the PC!
>
> What section of the Admin manual do you believe I should read? I just browsed
> through it once again and could not find anything specific to this situation.
>
> Cheers,
>
> Boris.
>
>
> On Tue, Mar 3, 2015 at 4:02 PM, Stephen Wittstruck <[email protected]
> <mailto:[email protected]>> wrote:
> Boris,
>
> This config should be covered in the admin guide, at least it is for Cisco
> and port-security VLAN changes. The guide says to use the Voice VLAN
> interface command but we’ve inadvertently tested recently a trunk interface
> and PF switched the data Native VLAN on the trunk. I’ve done a lot of
> port-security straight up switch port, i.e. not VoIP, successful testing over
> the years in a lab environment (we’re still not production), but have been
> dragging my feet on testing Polycom VoIP attached PC’s, I guess the ‘VoIP
> attached PC dilemma’ has me procrastinating, i.e. the admin guides say the
> VoIP phone reboots on the VLAN change port bounce but the attached PC is said
> to not initiate DHCP’, I guess we’re hoping/reasoning that the attached PC’s
> change location/phone’s infrequently enough that we can live with manually
> forcing the PC to initiate DHCP by unplugging the cable or rebooting the
> machine. I really need to stop procrastinating and test this.
>
> Steve
> CSM
>
>
>
> > On Mar 3, 2015, at 1:42 PM, Boris Epstein <[email protected]
> > <mailto:[email protected]>> wrote:
> >
> > Hello all,
> >
> > We use Polycom VOIP phones that have an ethernet bridge with an ethernet
> > port to plug your PC in. While that PC gets to communicate with the rest of
> > the network using its MAC address and the ARP table on the switch gets that
> > MAC address it is the Polycom phone's MAC address that PF gets. Strangely
> > enough,once you register it in the PF only the PC gets moved to the
> > appropriate production VLAN - the phone itself stays in the voice VLAN
> > where it belongs. But I really would like to see and operate with the PC's
> > MAC address.
> >
> > Has anybody attempted this sort of a setup? Any advice on how to proceed?
> >
> > Thanks.
> >
> > Boris.
> > ------------------------------------------------------------------------------
> > Dive into the World of Parallel Programming The Go Parallel Website,
> > sponsored
> > by Intel and developed in partnership with Slashdot Media, is your hub for
> > all
> > things parallel software development, from weekly thought leadership blogs
> > to
> > news, videos, case studies, tutorials and more. Take a look and join the
> > conversation now.
> > http://goparallel.sourceforge.net/_______________________________________________
> >
> > <http://goparallel.sourceforge.net/_______________________________________________>
> > PacketFence-users mailing list
> > [email protected]
> > <mailto:[email protected]>
> > https://lists.sourceforge.net/lists/listinfo/packetfence-users
> > <https://lists.sourceforge.net/lists/listinfo/packetfence-users>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> <http://goparallel.sourceforge.net/>
> _______________________________________________
> PacketFence-users mailing list
> [email protected]
> <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
> <https://lists.sourceforge.net/lists/listinfo/packetfence-users>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website, sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for all
> things parallel software development, from weekly thought leadership blogs to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now.
> http://goparallel.sourceforge.net/_______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
