Re: [j-nsp] Aggregated Ethernet QoS
Hi Paul, You will apply CoS/QoS configurations on AE interface not on AE members. Regards, Muhammad Farooq From: waller...@hotmail.com To: juniper-nsp@puck.nether.net Date: Fri, 7 May 2010 14:58:29 +1000 Subject: [j-nsp] Aggregated Ethernet QoS Hi all, I can't find any documentation on CoS/QoS configuration on Aggregated Ethernet from Junipers web site, if anyone knows any links pls share. I know what configuration I want to do I'm just not sure where it has to be applied i.e on Gig interface, AE interface or ex interfaces. Regards Paul _ New, Used, Demo, Dealer or Private? Find it at CarPoint.com.au http://clk.atdmt.com/NMN/go/206222968/direct/01/ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Aggregated Ethernet QoS
Please also find below link covering all required configurations for CoS/QoS in JUNOS. http://jnpr.net/techpubs/en_US/junos10.1/information-products/topic-collections/config-guide-cos/config-guide-cos-TOC.html Regards, Muhammad Farooq From: scorpian...@hotmail.com To: waller...@hotmail.com; juniper-nsp@puck.nether.net Date: Fri, 7 May 2010 05:55:59 + Subject: Re: [j-nsp] Aggregated Ethernet QoS Hi Paul, You will apply CoS/QoS configurations on AE interface not on AE members. Regards, Muhammad Farooq From: waller...@hotmail.com To: juniper-nsp@puck.nether.net Date: Fri, 7 May 2010 14:58:29 +1000 Subject: [j-nsp] Aggregated Ethernet QoS Hi all, I can't find any documentation on CoS/QoS configuration on Aggregated Ethernet from Junipers web site, if anyone knows any links pls share. I know what configuration I want to do I'm just not sure where it has to be applied i.e on Gig interface, AE interface or ex interfaces. Regards Paul _ New, Used, Demo, Dealer or Private? Find it at CarPoint.com.au http://clk.atdmt.com/NMN/go/206222968/direct/01/ ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _ Hotmail: Trusted email with powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp _ Hotmail: Powerful Free email with security by Microsoft. https://signup.live.com/signup.aspx?id=60969 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] PBR JUNOS
Experts,
I have a PBR question.
Suppose I have a following firewall filter..
term 1 {
from destination-port [http https]
}
then routing-instance test;
term 2 {
then accept;
routing-instance test {
instance-type forwarding;
{
routing-option static route 0/0 next-hop 192.168.1.1/30
}
}
interface fe-2/0/0 {
unit 0 {
family inet {
address 192.168.1.2/30
}
}
}
Now if interface fe-2/0/0 goes down and route removed form routing table. Then
what will be the flow of HTTP and HTTPS traffic. Traffic will be droped or will
match to term 2?
or can we bypass PBR in case interface fe-2/0/0 goes down?
Thanks in advance
_
Windows Live Hotmail: Your friends can get your Facebook updates, right from
Hotmail®.
http://www.microsoft.com/middleeast/windows/windowslive/see-it-in-action/social-network-basics.aspx?ocid=PID23461::T:WLMTAGL:ON:WL:en-xm:SI_SB_4:092009
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] ISIS Case Study in JNCIP..Summarization into Backbone
Hi Hoogen,
Your understanding is perfect. When requirement is to redistribute aggregate
into backbone, then it is good, infact ideal practice to suppress more specific
routes although it is explicitly not required.
Regards,
Farooq
Date: Fri, 18 Sep 2009 01:16:16 -0700
From: hooge...@gmail.com
To: juni...@groupstudy.com; juniper-nsp@puck.nether.net
Subject: [j-nsp] ISIS Case Study in JNCIP..Summarization into Backbone
Hi,
My question is when we redistribute 172.16.40.0/30 and 172.16.40.4/30 subnet
on R6 and R7...it reaches R5... and we see the output as
l...@r5# run show route 172.16.40.0/29
inet.0: 29 destinations, 29 routes (29 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
172.16.40.0/30 *[IS-IS/15] 00:17:21, metric 6
to 10.0.8.5 via ge-0/0/0.0
172.16.40.4/30 *[IS-IS/15] 00:16:53, metric 6
to 10.0.8.10 via ge-0/0/1.0
[edit]
l...@r5#
Now we need to summarize this before sending it into Backbone..
On R5 though we see the policy-option to be
term 3 {
from {
protocol aggregate;
route-filter 172.16.40.0/29 exact;
}
to level 2;
then accept;
}
}
In this we have it accepting aggregate route 172.16.40/29
Now in the whole policy on R5 we do not discard the more specific routes
from entering the Backbone area
And on R3 we see those three routes along with the aggregate route...
l...@r3# run show route 172.16.40.0/29
inet.0: 25 destinations, 25 routes (25 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
172.16.40.0/29 *[IS-IS/165] 00:04:07, metric 13
to 10.0.2.1 via t1-2/0/0.35
172.16.40.0/30 *[IS-IS/18] 00:12:15, metric 9
to 10.0.2.1 via t1-2/0/0.35
172.16.40.4/30 *[IS-IS/18] 00:11:47, metric 9
to 10.0.2.1 via t1-2/0/0.35
[edit]
l...@r3#
Now from my understanding of the question I need to deny the longer more
specific routes... on R5 filter saying 172.16.40/29 longer the reject...
So that on R3 and R4 I only see
l...@r3# run show route 172.16.40.0/29
inet.0: 23 destinations, 23 routes (23 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
172.16.40.0/29 *[IS-IS/165] 00:04:29, metric 13
to 10.0.2.1 via t1-2/0/0.35
[edit]
l...@r3#
Is my understanding right.. or is this step not required ...I do not see
this extra solution in the book..
-Hoogen
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
_
More than messages–check out the rest of the Windows Live™.
http://www.microsoft.com/windows/windowslive/
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] ATM config
Hi Clue,
Your configurations for below mentioned requirement will be as follows in JUNOS.
Suppose you have installed atm pic in fpc 0 pic slot 0.
Configuration for Internet PVC
at-0/0/0 {
mtu 9192;
encapsulation atm-pvc;
atm-options {
pic-type atm2;
promiscuous-mode {
vpi 3;
}
}
unit 101 {
description ***Internet PVC***;
encapsulation atm-snap;
vci 3.101;
family inet {
mtu 1500;
address x.x.x.x/30;
}
}
Configuration for atm cross connect
at-0/0/0 {
mtu 9192;
encapsulation atm-pvc;
atm-options {
pic-type atm2;
promiscuous-mode {
vpi 3;
}
}
unit 102 {
description 1st pvc from Provider to be switched;
encapsulation atm-ccc-cell-relay;
vci 3.102;
}
}
at-0/0/1 {
mtu 9192;
encapsulation atm-pvc;
atm-options {
pic-type atm2;
promiscuous-mode {
vpi 3; # suppose you are using same vp at cisco side too. you can
change here if you want
}
}
unit 102 {
description 1st pvc to Cisco to be switched;
encapsulation atm-ccc-cell-relay;
vci 3.102;
}
}
protocols {
connections {
interface-switch provider-to-cisco-1st-pvc {
interface at-0/0/0.102;
interface at-0/0/1.102;
}
}
}
Similarly you will switch the second pvc.
Regards,
Farooq
Date: Thu, 27 Aug 2009 09:33:05 -0500
From: cluest...@gmail.com
To: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] ATM config
I have found some info about frame-relay CCC and I would imagine the ATM CCC
would be similar, but I am a little confused as to which CCC variant of ATM
I will need and it can still land one of those PVC's on the m10i doing the
switching.
[edit]
interfaces {
so-1/0/0 {
encapsulation
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary112.html#2216533
frame-relay-ccc;
unit
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary421.html#1017673
1 {
point-to-point
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary292.html#1016678;
eui-64
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary122.html#1320392
frame-relay-ccc;
dlci
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary100.html#2083014
600;
}
}
so-2/0/0 {
encapsulation
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary112.html#2216533
frame-relay-ccc;
unit 2 {
point-to-point;
encapsulation frame-relay-ccc;
dlci
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary100.html#2083014
750;
}
}
}
protocols {
connections
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary75.html#1014816
{
interface-switch
http://www.juniper.net/techpubs/software/junos/junos76/swconfig76-network-interfaces/html/interfaces-summary169.html#1015803
router-a-router-c {
interface so-1/0/0.1;
interface so-2/0/0.2;
}
}
mpls {
interface all;
}
}
On Wed, Aug 26, 2009 at 10:42 PM, Clue Store cluest...@gmail.com wrote:
Hi List,
I have a situation where I need to take 3 PVC's that I am getting from a
provider and land one of them on an ATM interface (OC-3) and possibly
cross-connect the others to the second port in the PIC to send to another
router (basically performing an ATM switch functionality). Can this be done
on a 2x OC-3 ATM, SMIR PIC on a m10i ?? And if so, can someone point me to
some config samples as to how to do this?? I imagine this would be a CCC
on interface, but I am a complete noob when it comes to ATM on the juniper.
Relevent configs of what I need to do are below.
Current Cisco config...
interface ATM2/0
no ip address
ip route-cache flow
load-interval 30
no atm ilmi-keepalive
!
interface ATM2/0.1 point-to-point -- PVC I wish
to terminate on the first OC-3 Port
description ***Internet PVC***
ip address x.x.x.x 255.255.255.252
pvc 3/101
protocol ip x.x.x.x broadcast
ubr 75000
encapsulation aal5snap
!
!
interface ATM2/0.2 point-to-point 1st PVC
CCC to the second port to connect back to the cisco
description Customer1 T1 #1
ip address x.x.x.x 255.255.255.252
pvc 3/102
protocol ip x.x.x.x broadcast
ubr 75000
encapsulation aal5snap
!
!
interface ATM2/0.3 point-to-point 2nd PVC
CCC to the second
