[c-nsp] vlan configuration for video system

[Nick Griffin]

What I'm saying is there are not a lot of ways to dynamically assign those
video devices/ports to certain vlans. You may look into VMPS, it can do vlan
assignments based on mac address, but it requires a switch capable of being
the server. Designate ports 1-X for video and put them in your video vlan.
Configure them for priority queuing and the switch to "mls qos trust dscp".

On 4/13/07, Dan <dan at technc.com> wrote:
>
> Thanks for your reply.
>
> We are not implementing a voip system yet but if we do the phones we buy
> will support cdp.  So that would be fine.
>
> So from what I gather, our video system has to be able to mark packets
> with a dscp value, which it does.  Separate Vlan's are recommended.
>
> So the only thing I need yet is a way for the switch to put a video
> device into the "video" vlan when its plugged in.  Is there a way to do
> this with acl's?  Would specified address help?
>
> The quality across the wireless links has been taken care of.  That is
> not a concern to me.
>
> Thanks,
> Dan.
>
>
> Nick Griffin wrote:
> > The only mechanism I know of on a switch to be able to determine what
> > vlan a port should be assigned to is the communication between a cisco
> > phone and switch utilizing CDP. There are of course other external
> > options, but thats more along the lines of security and Cisco ACS. I
> > wouldn't imagine the capability or the need to trunk to a video
> > system. Typically the video systems will set DSCP values for their
> > control and video traffic which you would configured your switch to
> > "trust". If for some reason they wouldn't mark they data, you would
> > use an extended acl to identify the traffic and set the DSCP value
> > accordingly. Some systems also use RSVP to request the reservation
> > from the network. I would recommend separate voice video and data
> > vlans to allow the different levels of QoS required for each
> > respective application. I would have a more of a concern with being
> > able to control quality across those wireless links if video will be
> > running across them.
> >
> > HTH,
> >
> > Nick Griffin, CCIE #17381
> >
> > On 4/12/07, *Dan Letkeman* <dan at technc.com <mailto:dan at technc.com>>
> > wrote:
> >
> >     Thats what I was afraid of having to do.  Its polycom vsx 6000's
> >     that we are
> >     using.  They do have the capability of marking packets with dscp
> >     so I could
> >     do that.  I guess without having vlan tagging on the polycom
> >     equipment there
> >     is no way for the switch to know what vlan that unit is supposed
> >     to be on?
> >     Dan
> >
> >
> >
> >     -----Original Message-----
> >
> >     From: "Voll, Scott" <Scott.Voll at wesd.org <mailto:Scott.Voll at wesd.org
> >>
> >
> >     To: "Dan" <dan at technc.com <mailto:dan at technc.com>>,
> >     <cisco-nsp at puck.nether.net <mailto:cisco-nsp at puck.nether.net>>
> >
> >     Date: Thu, 12 Apr 2007 14:54:53 -0700
> >
> >     Subject: RE: [c-nsp] vlan configuration for video system
> >
> >
> >
> >
> >     What kind of video system?  Does it mark packets with DSCP / IP
> >     Prec by
> >
> >     default?
> >
> >
> >
> >     My guess is that if your going to make a separate video vlan, you
> >     will
> >
> >     have to assign the port to the video vlan manually.  ( more
> Management
> >
> >     :-(
> >
> >
> >
> >     Scott
> >
> >
> >
> >     -----Original Message-----
> >
> >     From: cisco-nsp-bounces at puck.nether.net
> >     <mailto:cisco-nsp-bounces at puck.nether.net>
> >
> >     [mailto:cisco-nsp-bounces at puck.nether.net
> >     <mailto:cisco-nsp-bounces at puck.nether.net>] On Behalf Of Dan
> >
> >     Sent: Thursday, April 12, 2007 1:26 PM
> >
> >     To: cisco-nsp at puck.nether.net <mailto:cisco-nsp at puck.nether.net>
> >
> >     Subject: [c-nsp] vlan configuration for video system
> >
> >
> >
> >     Hello
> >
> >
> >
> >     We are implementing a video conferencing system on our system and
> >     I was
> >
> >     wondering  if anyone had recommendations for how to setup the
> >     vlan's for
> >
> >
> >
> >     data/video/voice.
> >
> >
> >
> >     We currently have one 3560 in each of the buildings and 2-10 2960's
> >
> >     behind the 3560.  All of the buildings are connected via wireless
> >
> >     bridges.
> >
> >
> >
> >     Should I create a separate vlan for voice, video, data, and
> management
> >
> >     in each building?
> >
> >
> >
> >     If I do create a separate vlan for each piece, how do the switches
> >     know
> >
> >     how to put say a video device on the video vlan when its connected
> on
> >
> >     the switch?
> >
> >
> >
> >     If there are any other suggestions please let me know as I'm open
> >     to any
> >
> >
> >
> >     options so I can make this system easy to manage and work well.
> >
> >
> >
> >     Thanks,
> >
> >     Dan.
> >
> >
> >
> >     _______________________________________________
> >
> >     cisco-nsp mailing list  cisco-nsp at puck.nether.net
> >     <mailto:cisco-nsp at puck.nether.net>
> >
> >     https://puck.nether.net/mailman/listinfo/cisco-nsp
> >     [https://puck.nether.net/mailman/listinfo/cisco-nsp]
> >
> >     archive at http://puck.nether.net/pipermail/cisco-nsp/
> >     [http://puck.nether.net/pipermail/cisco-nsp/]
> >     _______________________________________________
> >     cisco-nsp mailing list   cisco-nsp at puck.nether.net
> >     <mailto:cisco-nsp at puck.nether.net>
> >     https://puck.nether.net/mailman/listinfo/cisco-nsp
> >     archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> >
>
>
>