Re: [j-nsp] Interface group based on description

2013-10-30 Thread Nikita Shirokov
On the other hand we prefer external scripting (mostly m4 in our case) for generating configuration + load set terminal. It gives more features + you can link it with external tools (such as bgpq3 etc) — Sent from Mailbox for iPhone On Thu, Oct 31, 2013 at 9:48 AM, Crist Clark wrote: > If you

Re: [j-nsp] Interface group based on description

2013-10-30 Thread Crist Clark
If you want to start down the commit script rabbit hole to do this, here is a good start: http://www.juniper.net/us/en/community/junos/script-automation/library/configuration/backbone-mtu/ On Wed, Oct 30, 2013 at 2:50 PM, Brad Fleming wrote: > Does anyone know any tricks for creating a groupi

[j-nsp] Interface group based on description

2013-10-30 Thread Brad Fleming
Does anyone know any tricks for creating a grouping of interfaces based on the description attached? For example: Any logical interface with the label “BACKBONE to far-node” goes into a group that could then be referenced in OSPF, LDP, RSVP, etc. An interface-range is close but doesn’t allow you

[j-nsp] lsq interfaces on the M20?

2013-10-30 Thread Tim Howe
I can't seem to find a definitive answer in any documentation (the m20 pic guide, the cos configuration guide) as to whether I can do CoS with my bonded T1s. I have a CHDS3-QPP card, and setting a scheduler-map on those interfaces works like a champ. However, that doesn't seem to have any effect

[j-nsp] Fwd: SRX IPSEC Full Mesh

2013-10-30 Thread Mohammad Khalil
Hi all I have resolved the issue by configuring the second IP address of the tunnel to a different unit BR, Mohammad -- Forwarded message -- From: Mohammad Khalil Date: Tue, Oct 29, 2013 at 5:28 PM Subject: SRX IPSEC Full Mesh To: "juniper-nsp@puck.nether.net" Hi all I have th