Mailing List Archive

On Wed, Oct 30, 2002 at 07:08:41AM -0500, NKombiyil@bloomberg.com wrote:

> Does anyone know if CoS configuration is supported on the ATM (stm-1
> in my case) interfaces?

No, unless it's a ATM2 PIC

/Jesper

--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
Senior network engineer @ AS3292, TDC Tele Danmark

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.

Jesper,

Do u know how much cost an OC-3 ATM2 PIC ?

Luciano

-----Mensaje original-----
De: juniper-nsp-admin@puck.nether.net
[mailto:juniper-nsp-admin@puck.nether.net]En nombre de Jesper Skriver
Enviado el: Miercoles, 30 de Octubre de 2002 11:11 a.m.
Para: NKombiyil@bloomberg.com
CC: juniper-nsp@puck.nether.net
Asunto: Re: [j-nsp] CoS


On Wed, Oct 30, 2002 at 07:08:41AM -0500, NKombiyil@bloomberg.com wrote:

> Does anyone know if CoS configuration is supported on the ATM (stm-1
> in my case) interfaces?

No, unless it's a ATM2 PIC

/Jesper

--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
Senior network engineer @ AS3292, TDC Tele Danmark

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp

> From: NKombiyil@bloomberg.com
> Sender: juniper-nsp-admin@puck.nether.net
> Date: Wed, 30 Oct 2002 07:08:41 -0500
>
> Does anyone know if CoS configuration is supported on the ATM (stm-1 in my case) interfaces?

It's not officially supported for ATM1 cards. It will be on the new
ATM2 cards. It should work on ATM1 cards IF you only have a single VC
running on it. (That's usually not too useful.)

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman@es.net Phone: +1 510 486-8634

On Wed, Oct 30, 2002 at 11:41:25AM -0300, Luciano Salata wrote:
> Jesper,
>
> Do u know how much cost an OC-3 ATM2 PIC ?

As far as I know, it's the same price as the "old" ATM1 PIC's

/Jesper

--
Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
Senior network engineer @ AS3292, TDC Tele Danmark

One Unix to rule them all, One Resolver to find them,
One IP to bring them all and in the zone to bind them.

On 30.10.2002 11:41:25 +0000, Luciano Salata wrote:
> Jesper,
>
> Do u know how much cost an OC-3 ATM2 PIC ?

No, as prices varies. You'll have to contact your network supplier.

/Michael


> -----Mensaje original-----
> De: juniper-nsp-admin@puck.nether.net
> [mailto:juniper-nsp-admin@puck.nether.net]En nombre de Jesper Skriver
> Enviado el: Miercoles, 30 de Octubre de 2002 11:11 a.m.
> Para: NKombiyil@bloomberg.com
> CC: juniper-nsp@puck.nether.net
> Asunto: Re: [j-nsp] CoS
>
>
> On Wed, Oct 30, 2002 at 07:08:41AM -0500, NKombiyil@bloomberg.com wrote:
>
> > Does anyone know if CoS configuration is supported on the ATM (stm-1
> > in my case) interfaces?
>
> No, unless it's a ATM2 PIC
>
> /Jesper
>
> --
> Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456
> Senior network engineer @ AS3292, TDC Tele Danmark
>
> One Unix to rule them all, One Resolver to find them,
> One IP to bring them all and in the zone to bind them.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>

--
Michael Lyngbøl -- michael at lyngbol dot dk
Network Manager AS3292, TDC Tele Danmark

How could I tell it is an ATM1 or ATM2, by show chassis hardware?

----- Original Message -----
From: "Kevin Oberman" <oberman@es.net>
To: <NKombiyil@bloomberg.com>
Cc: <juniper-nsp@puck.nether.net>
Sent: Wednesday, October 30, 2002 10:49 PM
Subject: Re: [j-nsp] CoS


> > From: NKombiyil@bloomberg.com
> > Sender: juniper-nsp-admin@puck.nether.net
> > Date: Wed, 30 Oct 2002 07:08:41 -0500
> >
> > Does anyone know if CoS configuration is supported on the ATM (stm-1 in
my case) interfaces?
>
> It's not officially supported for ATM1 cards. It will be on the new
> ATM2 cards. It should work on ATM1 cards IF you only have a single VC
> running on it. (That's usually not too useful.)
>
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: oberman@es.net Phone: +1 510 486-8634
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>

Hi Everybody,

my question is....can we have one queue assigned to different interfaces and make that queue work independantly on each interface??

Is anybody have any solution to following:

We have a customer connected to our M5 on two sub interfaces and we are running two BGP sessions with him. His both the circuits are rate limited on sub interfaces to 10 MB. Now he wants that at any given time if one of the circuit is used less and other circuit have more bandwidth demand then the second circuit should be able to use first circuit's bandwidth and vica versa....is this possible with juniper????its ok if we need to change his circuit to one and then achive this on ip based rate limit or through queues or any other possible way.....


Pls if anybody have some sample configuration on this ...send me...it would be gr8 help for me....

thanks,



J.S.Grewal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030127/f32527c9/attachment.htm

On Mon, 27 Jan 2003 09:48:31 +0530
"jgrewal" <j.grewal@in.spectranet.com> wrote:

> my question is....can we have one queue assigned to different
> interfaces and make that queue work independantly on each
> interface??

By the wording of the rest of your message, I think you meant
interdependent, rather than independent. Juniper is the Perl of
routers, with more than one way to do things, but I don't believe there
is an easy way to do what you're looking for if its even at all
possible. You might be able to do something with forwarding based on a
policier, but I'm not sure I would recommend this in general. It might
be difficult to avoid rapid oscillation between the paths.

Perhaps something more along the lines of flow based load balancing,
would achieve the desired result? Doing so based on capacity or
utilization is going to be tricky. You'd also want to take into
consideration the return path, asymmetry routing and potential
packet-out-of-ordering issues that may result.

John

An HTML attachment was scrubbed...
URL: http://puck.nether.net/pipermail/juniper-nsp/attachments/20030219/a0c87107/attachment.htm