Re: [j-nsp] juniper trinity

[Nahrux M]

Please have look at the below link
EZchip Talks Juniper

http://www.lightreading.com/document.asp?doc_id=179122




On Sat, Oct 24, 2009 at 11:19 PM, Richard A Steenbergen 
wrote:

> On Sat, Oct 24, 2009 at 06:38:53PM +0200, magno wrote:
> > I repeat, Trinity has nothing to do with ez-chip. My advice is to stop
> > elucubrating around any ez-chip whatever.
> >
> > Ez-chip proved to be quite limited for some qos functions, so I really
> > don't think juniper wants to be qos feature limited by a third-party
> > chip anymore.
>
> I believe the original question was "do the new asics integrate the
> functionality of ezchip, thus eliminating the need for it", and from
> what I've heard I believe the answer is yes. That is why we're talking
> about the ezchip in the first place.
>
> --
> Richard A Steenbergenhttp://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] juniper trinity

[Richard A Steenbergen]

On Sat, Oct 24, 2009 at 06:38:53PM +0200, magno wrote:
> I repeat, Trinity has nothing to do with ez-chip. My advice is to stop
> elucubrating around any ez-chip whatever.
> 
> Ez-chip proved to be quite limited for some qos functions, so I really
> don't think juniper wants to be qos feature limited by a third-party
> chip anymore.

I believe the original question was "do the new asics integrate the
functionality of ezchip, thus eliminating the need for it", and from
what I've heard I believe the answer is yes. That is why we're talking
about the ezchip in the first place.

-- 
Richard A Steenbergenhttp://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] juniper trinity

[magno]

I repeat, Trinity has nothing to do with ez-chip. My advice is to stop
elucubrating around any ez-chip whatever.

Ez-chip proved to be quite limited for some qos functions, so I really
don't think juniper wants to be qos feature limited by a third-party
chip anymore.

My 2 cents.

 Max


On 24/10/2009, Richard A Steenbergen  wrote:
> On Sat, Oct 24, 2009 at 11:56:18AM +0200, Roger Gabarit wrote:
>> >
>> I'm sorry not to agree on this one. Unless you can prove me that I'm wrong
>> :)
>> - Juniper uses the chips on the MX series only in -Q- Line Cards. So when
>> you use something only in advanced QoS line cards, there's something
>> related
>> to QoS, definitely.
>>
>> - Check the description of EZChip NPs on their website (
>> http://www.ezchip.com), they are built to provide the Ethernet framing and
>> MAC lookup AND traffic management). Neither Cisco nor Juniper would buy a
>> chip to have it do only 20% of what it could do. Cisco uses the chip in
>> the
>> ES+/ES40 and in ASR 9k cards.
>
> Juniper uses EZChips on all MX series line cards, not just -Q. In fact,
> the distinction between the original MX DPCs and the -E models is the
> rev of EZChip, with the -E's having support for larger microcode (1.5KB
> vs 6KB). On regular switching/routing cards the EZChip is used only for
> framing and MAC lookup, all of the IP routing and QoS is handled by the
> I-Chip. I think you're actually right about the -Q cards, there is some
> EZChip QoS functionality used there to implement the per-VLAN features,
> but I (and one would assume most sane people with a budget :P) don't
> touch the -Q cards. :)
>
>> All that stuff makes me think that the 2 vendors will not release any 100G
>> ports (*with advanced QoS*) on MX or ASR until the EZChip NP4 is produced
>> (not only prototypes). That gives by the way > 2 years advance to
>> Alcatel-Lucent from that point of view, because their 100G NP has been
>> ready
>> since last year. Funny market :)
>>
>> But well, let's wait for Juniper's next week announcement.
>
> I don't think the Trinity announcement has anything to do with 100G, but
> I could be wrong.
>
> --
> Richard A Steenbergenhttp://www.e-gerbil.net/ras
> GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] [c-nsp] juniper trinity

[Richard A Steenbergen]

On Sat, Oct 24, 2009 at 11:56:18AM +0200, Roger Gabarit wrote:
> >
> I'm sorry not to agree on this one. Unless you can prove me that I'm wrong
> :)
> - Juniper uses the chips on the MX series only in -Q- Line Cards. So when
> you use something only in advanced QoS line cards, there's something related
> to QoS, definitely.
>
> - Check the description of EZChip NPs on their website (
> http://www.ezchip.com), they are built to provide the Ethernet framing and
> MAC lookup AND traffic management). Neither Cisco nor Juniper would buy a
> chip to have it do only 20% of what it could do. Cisco uses the chip in the
> ES+/ES40 and in ASR 9k cards.

Juniper uses EZChips on all MX series line cards, not just -Q. In fact,
the distinction between the original MX DPCs and the -E models is the
rev of EZChip, with the -E's having support for larger microcode (1.5KB
vs 6KB). On regular switching/routing cards the EZChip is used only for
framing and MAC lookup, all of the IP routing and QoS is handled by the
I-Chip. I think you're actually right about the -Q cards, there is some
EZChip QoS functionality used there to implement the per-VLAN features,
but I (and one would assume most sane people with a budget :P) don't
touch the -Q cards. :)

> All that stuff makes me think that the 2 vendors will not release any 100G
> ports (*with advanced QoS*) on MX or ASR until the EZChip NP4 is produced
> (not only prototypes). That gives by the way > 2 years advance to
> Alcatel-Lucent from that point of view, because their 100G NP has been ready
> since last year. Funny market :)
> 
> But well, let's wait for Juniper's next week announcement.

I don't think the Trinity announcement has anything to do with 100G, but 
I could be wrong.

-- 
Richard A Steenbergenhttp://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] [c-nsp] juniper trinity

[Derick Winkworth]

You are mistaken.  They use the ez-chip in non "Q" cards as well for the MX.

I think you only need to look at what the Q card does and you will see it does 
not marry up very well to the "traffic management" feature of the ez-chip... I 
think the previous poster was correct.  Ethernet framing and MAC lookup is all 
they are used for.





From: Roger Gabarit 
To: Richard A Steenbergen 
Cc: Juniper-Nsp ; cisco-...@puck.nether.net
Sent: Saturday, October 24, 2009 5:56:18 AM
Subject: Re: [j-nsp] [c-nsp] juniper trinity

>
> On Fri, Oct 23, 2009 at 12:54:40PM -0700, Marlon Duksa wrote:
> > This Trio or Trinity, whatever they call it is internally grown
> > technology...a combination if EZChip + I-chip functionality.
> >
> > Plus I don't think it is a good strategy for Juniper to use third party
> > vendors as this will not give them differentiation...
>
> I've heard people make this argument, but it is absurd. The only thing
> EZChip is used for on the MX is basic Ethernet framing and MAC lookup.
> No doubt it was much cheaper and easier for Juniper to use an off the
> shelf chip for this than to spin their own just to do this. To go from
> there to claiming that the rest of the forwarding/queuing/etc will be
> the same as a Cisco platform is absolutely insane, the only thing they
> have in common is the Ethernet frame.
>

I'm sorry not to agree on this one. Unless you can prove me that I'm wrong
:)
- Juniper uses the chips on the MX series only in -Q- Line Cards. So when
you use something only in advanced QoS line cards, there's something related
to QoS, definitely.
- Check the description of EZChip NPs on their website (
http://www.ezchip.com), they are built to provide the Ethernet framing and
MAC lookup AND traffic management). Neither Cisco nor Juniper would buy a
chip to have it do only 20% of what it could do. Cisco uses the chip in the
ES+/ES40 and in ASR 9k cards.

Quote :
EZchip’s NP-2 is a highly-flexible network processor with integrated traffic
managers providing wire-speed packet processing and advanced flow-based
bandwidth control. The NP-2 offers the speed of an ASIC combined with the
flexibility of a programmable microprocessor. It provides the silicon core
of next-generation Carrier Ethernet Switches and Routers (CESR). Through
programming the NP-2 delivers a variety of applications such as L2
switching, Q-in-Q, PBT, T-MPLS, VPLS, MPLS and IPv4/IPv6 routing. The
integrated traffic management provides advanced QoS for flow-based service
level agreements (SLA) and enabling triple-play services (voice, video,
data).

All that stuff makes me think that the 2 vendors will not release any 100G
ports (*with advanced QoS*) on MX or ASR until the EZChip NP4 is produced
(not only prototypes). That gives by the way > 2 years advance to
Alcatel-Lucent from that point of view, because their 100G NP has been ready
since last year. Funny market :)

But well, let's wait for Juniper's next week announcement.

Roger
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] Recover/Reset Passwd on juniper netscreen

[Masood Ahmad Shah]

I would go with power-it; you cannot recover the password without resetting
the unit to factory defaults. On other devices of Juniper like routers there
are ways to do this but not on firewall devices.

As you do not have copy of the current configuration, then I would say let
it run as long as it can without making any change and then reset and
reconfigure from scratch when you absolutely need to make a change.

Kind Regards,
Masood

-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of George
Sent: Saturday, October 24, 2009 1:09 PM
To: juniper-nsp@puck.nether.net
Subject: [j-nsp] Recover/Reset Passwd on juniper netscreen

Hello 

How do i recover/reset the root password on juniper netscreen 5gt.

I need a step by step guide guaranteed of working since I dont want to
lose my configs.

Regards
George
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] Recover/Reset Passwd on juniper netscreen

[George]

Hello 

How do i recover/reset the root password on juniper netscreen 5gt.

I need a step by step guide guaranteed of working since I dont want to
lose my configs.

Regards
George
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] [c-nsp] juniper trinity

[Roger Gabarit]

>
> On Fri, Oct 23, 2009 at 12:54:40PM -0700, Marlon Duksa wrote:
> > This Trio or Trinity, whatever they call it is internally grown
> > technology...a combination if EZChip + I-chip functionality.
> >
> > Plus I don't think it is a good strategy for Juniper to use third party
> > vendors as this will not give them differentiation...
>
> I've heard people make this argument, but it is absurd. The only thing
> EZChip is used for on the MX is basic Ethernet framing and MAC lookup.
> No doubt it was much cheaper and easier for Juniper to use an off the
> shelf chip for this than to spin their own just to do this. To go from
> there to claiming that the rest of the forwarding/queuing/etc will be
> the same as a Cisco platform is absolutely insane, the only thing they
> have in common is the Ethernet frame.
>

I'm sorry not to agree on this one. Unless you can prove me that I'm wrong
:)
- Juniper uses the chips on the MX series only in -Q- Line Cards. So when
you use something only in advanced QoS line cards, there's something related
to QoS, definitely.
- Check the description of EZChip NPs on their website (
http://www.ezchip.com), they are built to provide the Ethernet framing and
MAC lookup AND traffic management). Neither Cisco nor Juniper would buy a
chip to have it do only 20% of what it could do. Cisco uses the chip in the
ES+/ES40 and in ASR 9k cards.

Quote :
EZchip’s NP-2 is a highly-flexible network processor with integrated traffic
managers providing wire-speed packet processing and advanced flow-based
bandwidth control. The NP-2 offers the speed of an ASIC combined with the
flexibility of a programmable microprocessor. It provides the silicon core
of next-generation Carrier Ethernet Switches and Routers (CESR). Through
programming the NP-2 delivers a variety of applications such as L2
switching, Q-in-Q, PBT, T-MPLS, VPLS, MPLS and IPv4/IPv6 routing. The
integrated traffic management provides advanced QoS for flow-based service
level agreements (SLA) and enabling triple-play services (voice, video,
data).

All that stuff makes me think that the 2 vendors will not release any 100G
ports (*with advanced QoS*) on MX or ASR until the EZChip NP4 is produced
(not only prototypes). That gives by the way > 2 years advance to
Alcatel-Lucent from that point of view, because their 100G NP has been ready
since last year. Funny market :)

But well, let's wait for Juniper's next week announcement.

Roger
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp