Re: [j-nsp] REGEX

2017-09-25 Thread Jason Iannone
Try [0-9]{12,}

On Mon, Sep 25, 2017 at 11:53 AM, craig washington
 wrote:
> Hello all, hope this is the right place for this.
>
> I am not the best with Regex and was looking for an expression in a Juniper 
> that will match on only so many numbers.
>
> Meaning, I am looking at the mpls lsp statistics "show mpls lsp transit 
> statistics" and I only want to see the LSP's that have larger Bytes, for 
> instance I only want to see stuff that has at least 12 digits or longer.
>
>
>
> Any help would be greatly appreciated, and if this is the wrong thing to ask 
> here, I have no qualms with that either 
>
>
> Thanks again.
>
> ___
> 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] REGEX

2017-09-25 Thread craig washington
Hello all, hope this is the right place for this.

I am not the best with Regex and was looking for an expression in a Juniper 
that will match on only so many numbers.

Meaning, I am looking at the mpls lsp statistics "show mpls lsp transit 
statistics" and I only want to see the LSP's that have larger Bytes, for 
instance I only want to see stuff that has at least 12 digits or longer.



Any help would be greatly appreciated, and if this is the wrong thing to ask 
here, I have no qualms with that either 


Thanks again.

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

Re: [j-nsp] Combining two MS-MIC in MX104 for CGNAT

2017-09-25 Thread Pavel Lunin
Hi Aaron,

Yes, I had a customer with 2× MS-MICs in an MX104 in production. No major
issues with this so far.

They use nor ams neither rsp, just old-good per source IP FBF with bit
masks like this:

from source address 10.0.0.0/255.0.0.1 then routing-instance CGN-1 /*
10.x.x.a, a is even */
from source address 10.0.0.1/255.0.0.1 then routing-instance CGN-2 /*
10.x.x.b, b is odd */

With manual pools partitioning and some additional route leaking tricks to
make it redundant.

A major concern for CGN is that you want all sessions from the same source
IP to be nated to the same external address. Otherwise your support will
die under tons of "why my passive mode FTP/PPTP/IPsec don't work?"  This is
why basic ECMP is normally not the best option. No idea how ASM deals with
this, I think it should, but just be aware.

Pavel


2017-09-13 19:44 GMT+02:00 Aaron Gould :

> Has anyone tried this combing two MS-MIC-16G cards to accomplish higher
> CGNAT throughput ?
>
> -Aaron
>
> ___
> 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] logical system in production - MX960

2017-09-25 Thread Chuck Anderson
On Mon, Sep 25, 2017 at 07:10:47AM -0500, Aaron Gould wrote:
> A few questions about logical systems. related to a new 5-node MX960 100 gig
> ring.
> 
> Do you all use logical systems in your production environment ?

I do.

> Do you contain your core P functions inside of an lsys ?

My network is rather small and combines P/PE functions, so I guess the
answer is "yes".

> Is the master/hosting lsys completely absent of any and all provider routes,
> and does it only contain a simply management interface (fxp) and not much
> more than that ?

No, I use the main systems to run my LAN and a single WAN lsys on each
MX480.  They are interconnected by my firewalls.

> If you were deploying a 5-node MX960 mpls core for an ISP, would you deploy
> lsys's from the start and put the core routing inside an lsys ?

Maybe, but there are some limitations.  Some things don't work in
lsys, such as port-mirroring & inline-jflow sampling (although support
for the latter is supposed to be there in the latest Junos
releases--it was buggy/crashy and I had to turn it off).

https://www.juniper.net/documentation/en_US/junos/topics/concept/logical-systems-restrictions.html
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


[j-nsp] QFX 5100 and VLAN-CCC Unicast SNMP Counter wraping

2017-09-25 Thread Alain Hebert

    Hi,

    Is it common knowledge that the Unicast Packets (Both In & Out) 
COUNTER32 for VLAN-CCC wrap at 0x3fff instead of 0x?


Model: qfx5100-48s-6q
Junos: 17.2R1.13

    I have plenty of example from snmpget (sample taken every 10s) that 
show the counter around 0x3fff.  aka: 1,073,640,642 (0x3ffe74c2) 
before wrapping down into the 200k region. Which match my iperf of 80k 
pps running on that VLAN-CCC



    PS: Wasn't fun trying to explain that to JNP Level 1 JTAC guy.  I 
was really expecting that he would understand basic computer science 
concept as what is hex and what's wraping.


--
-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911  http://www.pubnix.netFax: 514-990-9443

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

[j-nsp] logical system in production - MX960

2017-09-25 Thread Aaron Gould
A few questions about logical systems. related to a new 5-node MX960 100 gig
ring.

 

Do you all use logical systems in your production environment ?

 

Do you contain your core P functions inside of an lsys ?

 

Is the master/hosting lsys completely absent of any and all provider routes,
and does it only contain a simply management interface (fxp) and not much
more than that ?

 

If you were deploying a 5-node MX960 mpls core for an ISP, would you deploy
lsys's from the start and put the core routing inside an lsys ?

 

I use lsys in my lab mx104 and have all p/pe/ce/c functions inside lots of
different lsys's.. but now I want to know how everyone uses lsys for
production as mentioned above.

 

-Aaron Gould

 

 

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