Re: Verizon MPLS service in Anchorage
On Thu, Feb 24, 2011 at 10:01 AM, Brandon Ross wrote: > On Thu, 24 Feb 2011, lists lists wrote: > > I'm seeing that packets marked as DSCP EF are given fantastic treatment >> (low >> jitter, no packet loss), but other packets, including AF41, AF31, and BE >> are >> given what appears to be the "junk bucket" treatment. >> > > Hah, just a few days ago I spoke with an "engineer" at VZ that tried to > claim that each of the treatments were different, but that they only charged > extra for EF. I asked why I shouldn't just put all my traffic in the > highest "free" treatment and beat out all the other customers for the best > treatment for mine. He told me that "most of his customers weren't trying > to get their traffic through at the expense of other customers". > > Anyway, despite what their "engineers" say, only EF is actually treated on > the VZ network better than BE, the rest are just to prioritize traffic at > your own egress port. > > -- > Brandon Ross AIM: > BrandonNRoss > ICQ: 2269442 > Skype: brandonross Yahoo: BrandonNRoss > Brandon, VZ does or can apply a PE-egress profile that handles traffic differently based on DSCP marking. Your account team should be able to provide this to you. As far as unique treatment within their P network, it sure looks to me that the higher AF classes do get better treatment. My problem is that non-EF is handled terribly, and it's causing a big problem with interactive traffic. Voice is fine. thanks.
Re: Verizon MPLS service in Anchorage
On Thu, Feb 24, 2011 at 10:01 AM, Brandon Ross wrote: > On Thu, 24 Feb 2011, lists lists wrote: > >> I'm seeing that packets marked as DSCP EF are given fantastic treatment >> (low >> jitter, no packet loss), but other packets, including AF41, AF31, and BE >> are >> given what appears to be the "junk bucket" treatment. > > Hah, just a few days ago I spoke with an "engineer" at VZ that tried to > claim that each of the treatments were different, but that they only charged > extra for EF. I asked why I shouldn't just put all my traffic in the > highest "free" treatment and beat out all the other customers for the best > treatment for mine. He told me that "most of his customers weren't trying > to get their traffic through at the expense of other customers". > > Anyway, despite what their "engineers" say, only EF is actually treated on > the VZ network better than BE, the rest are just to prioritize traffic at > your own egress port. 'at your egress port' .. or 'where you are attempting to put 10lbs of crap in a 5lb bag'.. chances are the anchorage node is actually a partner node anyway, fyi.
Re: Verizon MPLS service in Anchorage
On Thu, 24 Feb 2011, lists lists wrote: I'm seeing that packets marked as DSCP EF are given fantastic treatment (low jitter, no packet loss), but other packets, including AF41, AF31, and BE are given what appears to be the "junk bucket" treatment. Hah, just a few days ago I spoke with an "engineer" at VZ that tried to claim that each of the treatments were different, but that they only charged extra for EF. I asked why I shouldn't just put all my traffic in the highest "free" treatment and beat out all the other customers for the best treatment for mine. He told me that "most of his customers weren't trying to get their traffic through at the expense of other customers". Anyway, despite what their "engineers" say, only EF is actually treated on the VZ network better than BE, the rest are just to prioritize traffic at your own egress port. -- Brandon Ross AIM: BrandonNRoss ICQ: 2269442 Skype: brandonross Yahoo: BrandonNRoss
Verizon MPLS service in Anchorage
Hello, I've got a bunch of sites connected to the Verizon Private IP MPLS service, and recently brought online a location in Anchorage connected to the brand-new PE node in the same city. I'm seeing that packets marked as DSCP EF are given fantastic treatment (low jitter, no packet loss), but other packets, including AF41, AF31, and BE are given what appears to be the "junk bucket" treatment. I'm having a difficult time getting anyone to acknowledge this problem, but it's causing interactive applications to be unusable for times of the day. Can anyone point me in a good direction? thanks.
