I've seen this sort of a thing done on other platforms. The most you can expect
it to put the more specific match up front ( unit 1 } outer 555 inner 200 } )
followed by less specifics towards the end ( unit 20 { outer 555 } ).
But I'm guessing here, I've not seen this done and in
On (2014-07-21 00:16 -0700), Robert J Huey wrote:
I've seen this sort of a thing done on other platforms. The most you can
expect it to put the more specific match up front ( unit 1 } outer 555 inner
200 } ) followed by less specifics towards the end ( unit 20 { outer 555 } ).
I've
I meant having two subinterfaces with the four prospected scenarios.
Tks
Messaggio originale
Da: sth...@nethelp.no
Data:
A: dim0...@hotmail.com
Cc: juniper-nsp@puck.nether.net
Oggetto: Re: [j-nsp] QinQ interface configuration question
I'm wondering if under a QinQ
I meant having two subinterfaces with the four prospected scenarios.
Right, I believe that is what I replied. So let's do them once more
and see if it answers your questions. If not, you need to clarify
further. Interface ge-0/0/0 used as an example.
1) different SVLAN and CVLAN
interface
Yes, this is the point why it doesn't work.
Tks
Sent with Mobile
Messaggio originale
Da: Edward Dore edward.d...@freethought-internet.co.uk
Data:
A: dim0sal dim0...@hotmail.com
Cc: sth...@nethelp.no,juniper-nsp@puck.nether.net
Oggetto: Re: [j-nsp] QinQ interface
5 matches
Mail list logo
