Re: [j-nsp] Unit ID's and q-in-q
You can do this with a properly constructed XPath expression... I will look at this later in the lab Sent from Yahoo! Mail on Android ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Unit ID's and q-in-q
Derick Winkworth writes: > Just do it sequentially and then write an op script that takes the > vlan(s) as an argument to show you the interface info you are looking > for... I am looking at this option, but it seems that there is no Junoscript command to get all objects with elements matching a specific pattern. More specifically, I can't even ask for "all interfaces which have vlan-id=1010". Can this really be true? Obviously I can just ask for all interfaces and loop. /Benny ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Unit ID's and q-in-q
Dotted unit numbers is an interesting concept. Why not both? :-) On 27 December 2011 22:28, Benny Amorsen wrote: > Saku Ytti writes: > > > What ever you do, also open enhancement request. This is extremely > annoying > > and trivial to fix. > > (While at it JNPR, give us tags/colours to direct routes, kthx). > > Certainly. What would be your preferred enhancement, just larger unit > numbers or the ability to have unit ID's with dots in? > > If the commit check error message is to be believed, larger unit ID's > are already available for certain interface types (demux0 and pp0). > > > /Benny > > ___ > 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] Unit ID's and q-in-q
> > Certainly. What would be your preferred enhancement, just larger unit > > numbers or the ability to have unit ID's with dots in? > > Just larger unit numbers, it's most trivial to implement and will allow the > use > of the scheme you described, which I believe every one and their mum are using > in IOS. *And* in Juniper ERX/E-Series :-) Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Unit ID's and q-in-q
On (2011-12-27 23:28 +0100), Benny Amorsen wrote: > Certainly. What would be your preferred enhancement, just larger unit > numbers or the ability to have unit ID's with dots in? Just larger unit numbers, it's most trivial to implement and will allow the use of the scheme you described, which I believe every one and their mum are using in IOS. I'm happy to add our contract# to the ER (since vendors tend to tell always 'no one else has requested this', which invariably is just poor communication), so contact me directly to get our details for the ER. It's exceedingly annoying that once you deploy JunOS, you need to develop some software to manage unit number/vlan mapping, when you can do it statelessly in IOS. > If the commit check error message is to be believed, larger unit ID's > are already available for certain interface types (demux0 and pp0). Yes. And there is no reason not to support it everywhere, if there ever was some IFL = CLI unit * IFD mapping relation, it's long gone. I don't suspect it ever had any hardware parallel TAZ-TBB-0(mahrouter vty)# show ifl brief ... 366 ge-1/2/0.500 VLAN TaggedEthernet0xc000 367 ge-1/2/0.501 VLAN TaggedEthernet0xc000 368 ge-1/2/0.2636VLAN TaggedCCC/VLAN0x5000 369 ge-1/2/0.32767 VLAN TaggedEthernet0x0400c000 370 ge-1/2/1.32767 VLAN TaggedEthernet0x0400c000 ... Thanks, -- ++ytti ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Unit ID's and q-in-q
Saku Ytti writes: > What ever you do, also open enhancement request. This is extremely annoying > and trivial to fix. > (While at it JNPR, give us tags/colours to direct routes, kthx). Certainly. What would be your preferred enhancement, just larger unit numbers or the ability to have unit ID's with dots in? If the commit check error message is to be believed, larger unit ID's are already available for certain interface types (demux0 and pp0). /Benny ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Unit ID's and q-in-q
Derick Winkworth writes: > Just do it sequentially and then write an op script that takes the > vlan(s) as an argument to show you the interface info you are looking > for... Thank you all for your suggestions! I will try to see if a bit of scripting can save some work for me. I might still be able to get away with not storing the unit ID in the provisioning database. /Benny ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Unit ID's and q-in-q
On 27 December 2011 01:38, Saku Ytti wrote: > (While at it JNPR, give us tags/colours to direct routes, kthx). I second that, and would add 'communities' for direct routes as well. > > -- > ++ytti > ___ > 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] Unit ID's and q-in-q
On (2011-12-22 23:32 +0100), Benny Amorsen wrote: > I am wondering if any of you have suggestions for allocating unit > numbers for q-in-q interfaces on the MX platform. What ever you do, also open enhancement request. This is extremely annoying and trivial to fix. (While at it JNPR, give us tags/colours to direct routes, kthx). -- ++ytti ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Unit ID's and q-in-q
Hey there What I do is basically start at UNIT 1, do it sequentially, add a good description (maximum of information) and when trying to find a concrete customer afterwards, issue "show interface description | match [ge-x/y/z]" This is the easiest, I believe :-) -Mensaje original- De: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp-boun...@puck.nether.net] En nombre de Derick Winkworth Enviado el: viernes, 23 de diciembre de 2011 0:27 Para: juniper-nsp@puck.nether.net; benny+use...@amorsen.dk Asunto: Re: [j-nsp] Unit ID's and q-in-q Just do it sequentially and then write an op script that takes the vlan(s) as an argument to show you the interface info you are looking for... Sent from Yahoo! Mail on Android ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp Por favor, antes de imprimir este correo, valore si es estrictamente necesario. La naturaleza y el medio ambiente lo agradecerán. Le informamos, como destinatario de este mensaje, que el correo electrónico y las comunicaciones por medio de Internet no permiten asegurar ni garantizar la confidencialidad de los mensajes transmitidos, así como tampoco su integridad o su correcta recepción, por lo que TELECABLE DE ASTURIAS, S.A.U no asume responsabilidad alguna por tales circunstancias. Si no consintiese en la utilización del correo electrónico o de las comunicaciones vía Internet le rogamos nos lo comunique y ponga en nuestro conocimiento de manera inmediata. Este mensaje va dirigido, de manera exclusiva, a su destinatario y contiene información confidencial y sujeta al secreto profesional, cuya divulgación no está permitida por la ley. En caso de haber recibido este mensaje por error, le rogamos que, de forma inmediata, nos lo comunique mediante correo electrónico remitido a nuestra atención o a través del teléfono (+ 34) 984191000 y proceda a su eliminación, así como a la de cualquier documento adjunto al mismo. Asimismo, le comunicamos que la distribución, copia o utilización de este mensaje, o de cualquier documento adjunto al mismo, cualquiera que fuera su finalidad, están prohibidas por la ley. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Unit ID's and q-in-q
You could stick something in the description of the interface, like some sort of tag, and then just do a "show int desc | match ". Something along the lines of description "Customer X [qq=1010.7]"; or some such. No scripts or databases to maintain either, infact a script could automatically maintain a DB for you based on this kind of setup. :-) On 22 December 2011 23:26, Derick Winkworth wrote: > Just do it sequentially and then write an op script that takes the vlan(s) > as an argument to show you the interface info you are looking for... > > > Sent from Yahoo! Mail on Android > > ___ > 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] Unit ID's and q-in-q
Just do it sequentially and then write an op script that takes the vlan(s) as an argument to show you the interface info you are looking for... Sent from Yahoo! Mail on Android ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Unit ID's and q-in-q
I am wondering if any of you have suggestions for allocating unit numbers for q-in-q interfaces on the MX platform. For plain VLAN's it is quite easy; just use the VLAN as the unit ID. That does not work for q-in-q because unit numbers are integers. The obvious solution 1017 for outer 1010 inner 7 does not work either, as the unit ID seems to be limited to be at most 16384. Just adding them sequentially is a possibility, but with several hundred subinterfaces per physical interface it becomes challenging for operators to find the correct unit ID for a particular VLAN. Perhaps I will have to add a per-interface unit ID database to our provisioning system. Ideas are welcome! /Benny ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
