Service releases.
Le ven. 15 mars 2024 à 19:50, Joe Horton a écrit :
> SR (service release) release notes have been PDF for a while.
>
> Regular release notes are still available via web as previously.
>
>
>
> I’ll gladly pass along the feedback as well that SR notes need imp
SR (service release) release notes have been PDF for a while.
Regular release notes are still available via web as previously.
I’ll gladly pass along the feedback as well that SR notes need improvement.
Joe
Juniper Business Use Only
From: juniper-nsp on behalf of Olivier
Benghozi via juni
--- Begin Message ---
Yes those four points are all very valid.
Just wanted to clear up that using 100G didn’t “lose” the extra 40G of capacity.
Joe
From: Brian Johnson
Date: Wednesday, May 6, 2020 at 1:58 PM
To: Joe Horton
Cc: Tobias Heister , "juniper-nsp@puck.nether.net"
Subje
--- Begin Message ---
Brian,
I'm not sure who you team is, but the other guys are correct. You can
provision the addition ports using port mode.
Just enabling the 100G ports does not disable the use of the additional 40G.
Been there done that, fully supported.
If you've got something specific
--- Begin Message ---
First, I would like to clarify that yes you can provision up to 240G of
capacity per PFE/PIC on the MPC7.
It can be any combination of 100/40/10, just as long as the total doesn't go
over 240, noting that only certain ports are 100G capable.
Second, to Tobias' comments, yes
You actually don’t need the newer backplane chassis for the SCBE2. On the
original backplane chassis there is a slight reduction of available bandwidth
compared to the newer one, but it is still much higher than SCBE and worth the
upgrade to support newer modules even without a chassis swap.
J
Here is a quick summary of the JUNOS RSTP/VSTP interop behavior.
If you enable RSTP on the Juniper side, and do NOT set any native-vlans on any
of the cisco ports connected to juniper, then JUNOS will interop with the cisco
RSTP frames sent untagged, and VLAN1 will block correctly. The cisco de
Single image for
M5, M10, M7i, M10i, M20, M40, M40e, M120, M320, T320, T640, T1600,
TX-Matrix.
A different single image for
J2300, J4300, J6300, J2320, J2350, J4350, J6530.
Joe
Joe Horton
972-663-3010
mailto://[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto
You can do what you want by using "loopback groups" on the 50.
You define the loopback interface, place the NAT information you want to use
(MIP or DIP) on the loopback. Then tie the external interfaces to the
loopback via a loopback group.
Joe
Joe Horton
972-663-3010
mailto://[EMAIL
Glad to help.
Joe Horton
972-663-3010
mailto://[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Gabriel
Sent: Tuesday, July 17, 2007 9:26 AM
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] ns-50 NAT problem
>
> You
he tests for no cost after you pass an online pre-test and
pass it.
Joe
Joe Horton
972-663-3010
mailto://[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Stacy W. Smith
Sent: Wednesday, May 23, 2007 1:45 AM
To: juniper-nsp@puck.nether
gr-0/0/0 {
unit 1 {
tunnel {
source y.y.y.y;
destination x.x.x.x;
}
family inet {
address 10.1.10.2/30;
}
}
Joe Horton
972-663-3010
mailto://[EMAIL PROTECTED]
-Original
12 matches
Mail list logo
