[cisco-voip] Trusting CoS on router uplink from switch...

[Jonathan Charles]

That's what I thought... thanks to all... cuz inbound service policies
can only remark, not queue...


Jonathan

On Wed, Jul 23, 2008 at 12:12 PM,  <Thorsten.Mayr at barclayscapital.com> wrote:
> The only thing you can specify on the VG inbound is a cos-dscp or
> dscp-cos map which would save you the policy mark/remark in case needed
> and granted the fact that you have COS on the frame... (you'll probably
> not need to though)
>
> as Ryan already pointed out, there is no trust command or anything
> similar on the gateway )-:
>
> T
>
>> -----Original Message-----
>> From: Ryan West [mailto:rwest at zyedge.com]
>> Sent: Wednesday, July 23, 2008 6:02 PM
>> To: Jonathan Charles; Mayr, Thorsten: IT (LDN)
>> Cc: cisco-voip at puck.nether.net
>> Subject: RE: [cisco-voip] Trusting CoS on router uplink from switch...
>>
>> mls qos trust cos on the inbound dot1q trunk for the switch
>> and nothing on the router.  There is no trust for outbound.
>> You can test by putting the policy-map on the router match on
>> just dscp 46 with a secondary match on protocol rtp audio and
>> should have little to nothing show up in the rtp audio matches.
>>
>> -ryan
>>
>> -----Original Message-----
>> From: cisco-voip-bounces at puck.nether.net
>> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of
>> Jonathan Charles
>> Sent: Wednesday, July 23, 2008 12:39 PM
>> To: Thorsten.Mayr at barclayscapital.com
>> Cc: cisco-voip at puck.nether.net
>> Subject: Re: [cisco-voip] Trusting CoS on router uplink from switch...
>>
>> OK, so for inbound trusting on a dot1q, on a switchport, we do:
>>
>> mls qos trust cos
>>
>> How do you do it outbound, and then inbound on the voice gateway?
>>
>> It is a 2811 in the lab...
>>
>>
>>
>> Jonathan
>>
>> On Wed, Jul 23, 2008 at 11:38 AM,
>> <Thorsten.Mayr at barclayscapital.com> wrote:
>> > To cut it short yes. Trust the VG on the switch inbound to the
>> > switchport, and trust the switch inbound to the VG's port.
>> > What Gateway is it? 3800?
>> >
>> >
>> > Just my 2 cents, if someoen could confirm or correct where
>> I am wrong...
>> >
>> > Cheers
>> > T
>> >
>> > PS: sorry can't post to the ccie group yet - haven't subscribed yet.
>> >
>> >> -----Original Message-----
>> >> From: Jonathan Charles [mailto:jonvoip at gmail.com]
>> >> Sent: Wednesday, July 23, 2008 5:33 PM
>> >> To: Mayr, Thorsten: IT (LDN)
>> >> Cc: cisco-voip at puck.nether.net; ccie_voice at onlinestudylist.com
>> >> Subject: Re: [cisco-voip] Trusting CoS on router uplink
>> from switch...
>> >>
>> >> Cos is recommended (per the QoS SRND) for any dot1q trunk...
>> >>
>> >> However, my concern is not the switch, but the voice
>> gateway's Fast
>> >> Ethernet to the switch... Do we need to trust outbound (switch to
>> >> gateway), and inbound (on the gateway side...)
>> >>
>> >>
>> >>
>> >> Jonathan
>> >>
>> >> On Wed, Jul 23, 2008 at 11:28 AM,
>> >> <Thorsten.Mayr at barclayscapital.com> wrote:
>> >> > Someone correct me if wrong and might actually depend on
>> >> IOS and type
>> >> > of kit as well.
>> >> >
>> >> > As long as you don't have mls configured at all, you won't be
>> >> > rewriting the DSCP fields.
>> >> > If you have mls configured, you'll have to trust COS or
>> >> DSCP whatever
>> >> > you prefer otherwise you'll overwrite with default value.
>> >> >
>> >> > I am not sure if it's better to trust on DSCP or COS in
>> >> this case, If
>> >> > you are trunking you might as well stick to COS. Also
>> >> you'll have wrr
>> >> > or srr queues setup which will map to COS.
>> >> >
>> >> > Haven't touched qos for a while and seems like I do have to
>> >> freshen up
>> >> > on this topic ;)
>> >> >
>> >> >> -----Original Message-----
>> >> >> From: Jonathan Charles [mailto:jonvoip at gmail.com]
>> >> >> Sent: Wednesday, July 23, 2008 5:18 PM
>> >> >> To: Mayr, Thorsten: IT (LDN)
>> >> >> Cc: cisco voip; OSL CCIE Voice Lab Exam
>> >> >> Subject: Re: [cisco-voip] Trusting CoS on router uplink
>> >> from switch...
>> >> >>
>> >> >> Well, I do have subinterfaces and it is a dot1q trunk to the
>> >> >> gateway... just looking for a config to trust the CoS and
>> >> DSCP... or
>> >> >> wondering if the router will clear the DSCP and CoS....
>> >> >>
>> >> >>
>> >> >>
>> >> >> Jonathan
>> >> >>
>> >> >> On Wed, Jul 23, 2008 at 9:38 AM,
>> >> >> <Thorsten.Mayr at barclayscapital.com> wrote:
>> >> >> > Charles,
>> >> >> > You won't have COS on the link to the gateway as you
>> >> won't have a
>> >> >> > dot1.q/isl tag, unless you use subinterfaces on the router.
>> >> >> >
>> >> >> > I'd trusting on DSCP in that case.
>> >> >> >
>> >> >> > Did I get this one right, now? ;)
>> >> >> >
>> >> >> > T
>> >> >> >
>> >> >> >> -----Original Message-----
>> >> >> >> From: cisco-voip-bounces at puck.nether.net
>> >> >> >> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf
>> >> Of Jonathan
>> >> >> >> Charles
>> >> >> >> Sent: Wednesday, July 23, 2008 2:58 PM
>> >> >> >> To: cisco voip; OSL CCIE Voice Lab Exam
>> >> >> >> Subject: [cisco-voip] Trusting CoS on router uplink
>> >> from switch...
>> >> >> >>
>> >> >> >> OK, so we set the switch ports to trust CoS on the dot1q
>> >> >> trunk from
>> >> >> >> phone to switch... are these then trusted from that point
>> >> >> on, or do
>> >> >> >> we need to trust them elsewhere as well?
>> >> >> >>
>> >> >> >> Do we need to add any config to the voice gateways to
>> >> >> trust the CoS
>> >> >> >> coming from the switches?
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> Jonathan
>> >> >> >> _______________________________________________
>> >> >> >> cisco-voip mailing list
>> >> >> >> cisco-voip at puck.nether.net
>> >> >> >> https://puck.nether.net/mailman/listinfo/cisco-voip
>> >> >> >>
>> >> >> > _______________________________________________
>> >> >> >
>> >> >> > This e-mail may contain information that is confidential,
>> >> >> privileged or otherwise protected from disclosure. If you
>> >> are not an
>> >> >> intended recipient of this e-mail, do not duplicate or
>> >> redistribute
>> >> >> it by any means. Please delete it and any attachments and
>> >> notify the
>> >> >> sender that you have received it in error. Unless specifically
>> >> >> indicated, this e-mail is not an offer to buy or sell or a
>> >> >> solicitation to buy or sell any securities, investment
>> products or
>> >> >> other financial product or service, an official
>> >> confirmation of any
>> >> >> transaction, or an official statement of Barclays. Any views or
>> >> >> opinions presented are solely those of the author and do not
>> >> >> necessarily represent those of Barclays. This e-mail is
>> subject to
>> >> >> terms available at the following link:
>> >> >> www.barcap.com/emaildisclaimer. By messaging with Barclays you
>> >> >> consent to the foregoing.  Barclays Capital is the
>> >> investment banking
>> >> >> division of Barclays Bank PLC, a company registered in England
>> >> >> (number 1026167) with its registered office at 1
>> Churchill Place,
>> >> >> London, E14 5HP.  This email may relate to or be sent
>> from other
>> >> >> members of the Barclays Group.
>> >> >> > _______________________________________________
>> >> >> >
>> >> >>
>> >> > _______________________________________________
>> >> >
>> >> > This e-mail may contain information that is confidential,
>> >> privileged or otherwise protected from disclosure. If you
>> are not an
>> >> intended recipient of this e-mail, do not duplicate or
>> redistribute
>> >> it by any means. Please delete it and any attachments and
>> notify the
>> >> sender that you have received it in error. Unless specifically
>> >> indicated, this e-mail is not an offer to buy or sell or a
>> >> solicitation to buy or sell any securities, investment products or
>> >> other financial product or service, an official
>> confirmation of any
>> >> transaction, or an official statement of Barclays. Any views or
>> >> opinions presented are solely those of the author and do not
>> >> necessarily represent those of Barclays. This e-mail is subject to
>> >> terms available at the following link:
>> >> www.barcap.com/emaildisclaimer. By messaging with Barclays you
>> >> consent to the foregoing.  Barclays Capital is the
>> investment banking
>> >> division of Barclays Bank PLC, a company registered in England
>> >> (number 1026167) with its registered office at 1 Churchill Place,
>> >> London, E14 5HP.  This email may relate to or be sent from other
>> >> members of the Barclays Group.
>> >> > _______________________________________________
>> >> >
>> >>
>> > _______________________________________________
>> >
>> > This e-mail may contain information that is confidential,
>> privileged or otherwise protected from disclosure. If you are
>> not an intended recipient of this e-mail, do not duplicate or
>> redistribute it by any means. Please delete it and any
>> attachments and notify the sender that you have received it
>> in error. Unless specifically indicated, this e-mail is not
>> an offer to buy or sell or a solicitation to buy or sell any
>> securities, investment products or other financial product or
>> service, an official confirmation of any transaction, or an
>> official statement of Barclays. Any views or opinions
>> presented are solely those of the author and do not
>> necessarily represent those of Barclays. This e-mail is
>> subject to terms available at the following link:
>> www.barcap.com/emaildisclaimer. By messaging with Barclays
>> you consent to the foregoing.  Barclays Capital is the
>> investment banking division of Barclays Bank PLC, a company
>> registered in England (number 1026167) with its registered of!
>>  fice at 1 Churchill Place, London, E14 5HP.  This email may
>> relate to or be sent from other members of the Barclays Group.
>> > _______________________________________________
>> >
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
> _______________________________________________
>
> This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing.  Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP.  This email may relate to or be sent from other members of the Barclays Group.
> _______________________________________________
>