Re: [j-nsp] Advertise inactive route EBGP session

[Marcin Wojcik]

Hi Mileto,


>> I want to keep the static route configured in the router and advertise BGP
>> learned route to another eBGP peers. In my understanding the
>> advertise-inactive configuration inside the BGP group was supposed to work
>> in this scenario. I add this configuration, cleared the BGP session and I'm
>> still having problems to advertise the inactive route.

The advertise-inactive should have worked - maybe you have a mistake
in your export policy?


root@R1# run show route 9.9.9.9/32 table testri.inet.0

testri.inet.0: 15 destinations, 18 routes (15 active, 0 holddown, 0 hidden)
Restart Complete
+ = Active Route, - = Last Active, * = Both

9.9.9.9/32 *[Static/5] 00:00:53
  Discard
[BGP/170] 00:00:46, localpref 200
  AS path: 64555 I, validation-state: unverified
> to 11.11.11.6 via ge-1/2/0.0


root@R1-mx80# run show route advertising-protocol bgp 11.11.11.10 | match 9.9.9
  9.9.9.9/32  Self64555 I

[edit routing-instances testri protocols bgp]
root@R1# show
advertise-inactive;
group srx-1 {
neighbor 11.11.11.10 {
peer-as 64666;
}
}

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

Re: [j-nsp] Juniper MX VPLS S-Tag pop/push with QoS

[Marcin Wojcik]

Hi Mike,

I'd use 'learn-vlan-1p-priority X' in your filter in order to make
sure the QoS classification is based on the S-tag.
'user-vlan-1p-priority X' is useful if you want to base the
classification on the C-Tag.

Marcin.

On Fri, Nov 6, 2015 at 5:57 PM, Nealon, Mike  wrote:
> Hello, does anybody have knowledge of the order of operations relative to QoS 
> classification of a packet when using a pop/push mechanism in a VPLS 
> instance? I'm trying to make sure packets are classified based on the S-Tag 
> that I am "popping", but I fear the pop may happen before the classification. 
> I need the QoS/P-Bit information in the S-Tag to persist across the network. 
> So I guess the actual question is: How is QoS information persistence 
> achieved when you need to also provide VLAN ambiguity?
>
> Thanks all,
>
> -Mike
> ___
> 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 mx80 mirror ae0 to ge

[Marcin Wojcik]

Hi,

replace this set chassis fpc 1 pic 1 port-mirror-instance mirror_reductor with:
set chassis fpc 1 port-mirror-instance mirror_reductor

For whatever reason PM did not work (when I tested it  in the past)
when I tried to enable it for a particular pic. After enabling it for
fpc it worked ok.

Thanks,
Marcin.

On Tue, Jun 30, 2015 at 12:10 PM,  dmi...@zhigulinet.ru wrote:
 Hi, Juniper-nsp.

 I tried configure port mirrror on mx80, but i have problem I don't
 watch traffic on the port ge-1/0/5

 set chassis fpc 1 pic 1 port-mirror-instance mirror_reductor
 set forwarding-options port-mirroring instance mirror_reductor input rate 1
 set forwarding-options port-mirroring instance mirror_reductor input 
 run-length 0
 set forwarding-options port-mirroring instance mirror_reductor family inet 
 output interface ge-1/0/5.0 next-hop 192.168.98.2
 set forwarding-options port-mirroring instance mirror_reductor family inet 
 output no-filter-check
 set firewall filter mirror_reductor term dst-http-https from protocol tcp
 set firewall filter mirror_reductor term dst-http-https from destination-port 
 80
 set firewall filter mirror_reductor term dst-http-https from destination-port 
 443
 set firewall filter mirror_reductor term mirror then count mirror_reductor
 set firewall filter mirror_reductor term mirror then port-mirror-instance 
 mirror_reductor
 set firewall filter mirror_reductor term default then accept

 set interfaces ae0 unit 0 family inet filter input mirror_reductor


 set interfaces ge-1/0/5 description --mirror-to-reductor--
 set interfaces ge-1/0/5 unit 0 family inet address 192.168.98.1/30 arp 
 192.168.98.2 mac 00:11:22:33:44:55
 set forwarding-options port-mirroring instance mirror_reductor family inet 
 output interface ge-1/0/5.0 next-hop 192.168.98.2

 set interfaces ge-1/1/0 gigether-options 802.3ad ae0
 set interfaces ge-1/1/1 gigether-options 802.3ad ae0
 set interfaces ge-1/1/2 gigether-options 802.3ad ae0
 set interfaces ae0 unit 0 family inet address 123.143.143.246/30


 --
 Best regards
  Dmitry  mailto:dmi...@zhigulinet.ru

 ___
 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] CoS buffer size

[Marcin Wojcik]

Hi Dan,

 Seems odd to me that this needs to be done. Documentation I've read appears
 to suggest that in PIR mode (no guaranteed-rate set) the per-queue
 guarantee/transmit rate is calculated from the shaper rate and when a queue
 exceeds it's guaranteed rate it is in excess, but this doesn't appear to be
 the case and queues are always in excess.

That would be the case only if you use exact or rate-limit limit
options. When those options are omitted (percentage value only) then
the transmit rate is calculated on the parent interface PIR, hence,
one has to setup g-rate.

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

Re: [j-nsp] Difference between shaping-rate vs. transmit-rate?

[Marcin Wojcik]

Hi,

Think about shaping-rate as a PIR. If you won't set it, the default value
will be used - 100%. E.g. a particular queue can use all available
interface BW if the scheduler that is assigned to it is set with a
transmit-rate to 30% without setting up shaping-rate.

Thanks,
Marcin.



On Sat, Jun 20, 2015 at 7:39 PM, Pyxis LX pyxi...@gmail.com wrote:

 Hi, All.

 I'm quite confused about the differences between:
   shaping-rate
   transmit-rate (with rate-limit option turned on)

 Here's my understanding of transmit-rate under class-of-service (I'm
 not sure whether it's correct or not):

   1. The default setting is able to use the unused bw.

   2. If the exact option is turned on, the unused bw cannot be used
 by this queue. When the queue is transmitting over the transmit-rate,
 excess packets will be buffered. (Just like a policer with
 burst-size-limit != 0?)

   3. If the rate-limit option is turned on, the unused bw cannot be
 used. When the queue is transmitting over the transmit-rate, excess
 packets will be dropped. (Just like a policer with burst-size-limit =
 0?)

 The shaping-rate configures PIR, so it should act like variant 3?

 Thanks!
 ___
 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] Quick way to Shift MPLS traffic away from an interface

[Marcin Wojcik]

Hi,

I think this is what you are after:
switch-away-lsps

https://www.juniper.net/documentation/en_US/junos12.3/topics/reference/configuration-statement/switch-away-lsps-edit-protocols-mpls-interface.html

-Marcin.

On Wed, May 20, 2015 at 8:55 AM, tim tiriche tim.tiri...@gmail.com wrote:

 Hello,

 What is the quick way to shift LSP traffic from an interface after
 increasing the igp metric?

 question:

 - What command can I use to find all lsp traversing the iface and a good
 way to clear them? I am assuming I would need to run clear mpls
 optimize-aggressive on the lsp's on that particular router only? Is my
 understanding correct?

 - Is it a good idea to turn on optimize-aggressive?

 Any best practices or pointers would be appreciated!

 -Tim
 ___
 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